CVE-2026-14781: Keycloak-services: oidc email_verified claim incorrectly applied to userinfo email
Red Hat · Red Hat Build of Keycloak
Affected: Red Hat Build of Keycloak · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 20% of scored CVEs
DescriptionCVE.org
A flaw exists in the org.keycloak.broker.oidc package where the OIDC broker incorrectly synchronizes the email_verified claim. When an OIDC identity provider is configured with trustEmail=true and the userinfo endpoint is enabled, Keycloak retrieves the email address from the userinfo response but retrieves the email_verified status exclusively from the id_token. The root cause is a lack of validation ensuring that the email_verified claim in the id_token actually refers to the email address returned by the userinfo endpoint. If these two sources return different email addresses, the id_token's email_verified=true claim is blindly applied to the userinfo email. Exploitation Conditions: The OIDC identity provider must have trustEmail set to true (non-default). The userinfo endpoint must be enabled (default). The attacker must control or have compromised the upstream OIDC provider. Concrete Impact: Mark arbitrary email addresses as verified in the Keycloak database. Bypass email-based security controls or verification workflows. Potential account takeover if the application relies solely on the email_verified flag from the IdP to link accounts.
Affected products6
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Red Hat · Red Hat Build of KeycloakVersions not stated
- Red Hat · Red Hat Build of KeycloakVersions not stated
- Red Hat · Red Hat Build of KeycloakVersions not stated
- Red Hat · Red Hat Data Grid 8Versions not stated
- Red Hat · Red Hat JBoss Enterprise Application Platform Expansion PackVersions not stated
- Red Hat · Red Hat Single Sign-On 7Versions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
CoverageNo articles yet
No CyberSIXT article names CVE-2026-14781 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.