# CVE-2026-14781: Keycloak-services: keycloak-services: oidc email_verified claim incorrectly applied to userinfo email

> Attackers can mark arbitrary emails as verified by exploiting OIDC broker logic, potentially leading to account takeover if email verification is trusted.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** GHSA-c96p-56gh-3pvw

## What is CVE-2026-14781?

CVE-2026-14781 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-1288 (Improper Validation of Consistency within Input)

## Which versions are affected by CVE-2026-14781?

It affects 1 product.


Products: Redhat Build of Keycloak.

## How do I fix CVE-2026-14781?

No fix has been published for CVE-2026-14781 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-14781 being exploited?

There is no known exploitation of CVE-2026-14781 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Build of Keycloak

- [CVE-2026-15572](https://insights.sbomify.com/CVE-2026-15572/): Keycloak-services: keycloak-services: dcr protocol mapper type-swap policy bypass allows privilege escalation (high 8.8)
- [CVE-2026-3047](https://insights.sbomify.com/CVE-2026-3047/): Keycloak SAML Broken has Authentication Bypass by Primary Weakness (high 8.8)
- [CVE-2026-15573](https://insights.sbomify.com/CVE-2026-15573/): Keycloak-services: keycloak-services: authorization bypass via unnormalized uri matching in pathmatcher (high 8.1)
- [CVE-2026-16102](https://insights.sbomify.com/CVE-2026-16102/): Keycloak-services: keycloak-services: default dcr policy allows role forgery via user property mappers (high 8.1)
- [CVE-2026-1609](https://insights.sbomify.com/CVE-2026-1609/): Org.keycloak/keycloak-quarkus-server: keycloak: unauthorized access via jwt authorization grant with disabled users (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14781 and fix it if it is affected.

What it is: CVE-2026-14781 is a medium-severity vulnerability in Redhat Build of Keycloak, published on 5 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14781 in the wild and no public exploit code.

Affected product: Redhat Build of Keycloak. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-14781/ (Markdown: https://insights.sbomify.com/CVE-2026-14781/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-14781
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-14781
- OSV: https://osv.dev/vulnerability/CVE-2026-14781

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-14781/
Summaries are generated and may contain mistakes; the official description above is the record.