# CVE-2026-96445: Keycloak-services: keycloak-services: conditional otp skip-header policy evaluated against untrusted proxy headers

> Attackers with valid passwords can bypass two-factor authentication by spoofing untrusted proxy headers in Keycloak's conditional OTP policy.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-jj9w-64w4-2wcx

## What is CVE-2026-96445?

CVE-2026-96445 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in the Conditional OTP authenticator of Keycloak, an identity and access management solution. The issue occurs when the system evaluates specific HTTP headers to determine if a one-time password (OTP) should be skipped, but fails to verify if those headers came from a trusted source. This could allow an attacker who already has a user's password to bypass the second-factor authentication by providing a specially crafted header in their request.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-96445 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-96445 is a medium-severity authentication bypass vulnerability in Red Hat Build of Keycloak, published on 23 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-96445 in the wild and no public exploit code.

Affected product: Red Hat 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-96445/ (Markdown: https://insights.sbomify.com/CVE-2026-96445/index.md)
```

## Sources

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

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