CVE-2026-14781 Build of Keycloak
| Affected software | Build of Keycloak |
|---|---|
| Severity | 4.8 Medium CVSS 3.1 |
| Weakness | CWE-1288 |
| Published | 5 Jul 2026 |
| Updated | 11 Aug 2026 |
Description
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.
Exploitation status
No public exploit
No exploit has been reported in the sources we check.
Exploitation status
- CISA KEV not listed
- VulnCheck KEV not listed
- CISA Vulnrichment exploitation: none
- Indexed PoC none indexed
- EPSS 0.28% chance in 30 days
Waratek protection
Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.
A public code fix exists.
- Protection none
- Action unverified
- Review automated Upstream data
- Record active
| Decided by | Medium or Low severity, no CISA or VulnCheck KEV listing, no PoC clearing the evidence bar, no CISA verdict, no Oracle advisory |
|---|---|
| Finding | This CVE is MEDIUM severity, is not listed in CISA KEV or VulnCheck KEV, has no public exploit or PoC in any indexed source, carries no CISA Vulnrichment finding of a demonstrated exploit, and is not part of an Oracle Critical Patch Update. None of the signals that would put it in front of an engineer is present, and the volume of CVEs below that bar is too great to take one at a time, so no rule is written for it. This is a decision about what we act on, not a finding that the CVE is harmless — a patch may well be derivable, and a low-severity defect can still be one link in a longer chain. |
| Candidate fix | https://bugzilla.redhat.com/show_bug.cgi?id=2497118 : a Red Hat bug: the triage, which links onward to the fix |
Affected software and releases
Products and versions
1 product, 1 version entry| Source | Vendor | Product | Scheme | Affected versions |
|---|---|---|---|---|
| nvd | redhat | build of keycloak | generic | any version |
References
| URL | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=2497118 | bugzilla |
| https://access.redhat.com/security/cve/CVE-2026-14781 | Vendor Advisory |
Timeline
Timeline
| Published | 2026-07-05 | By the CVE Program. |
|---|---|---|
| NVD record modified | 2026-08-11 | NVD's own last-modified date for this record. |