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.
CVE-2026-96445
Score 6.8 from GitHub Security Advisory published 2026-09-23. a secondary CVSS source baseline 6.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.8
- EG Score
- 6.8(high)
- EG Risk
- 31(Track)EG Risk 31/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity68% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 14%
- KEV
- Not listed
Published
September 23, 2026
Last Modified
September 24, 2026
Advisory Details (2)
Auto-updated Sep 23, 20262539280 – (CVE-2026-96445) CVE-2026-96445 keycloak-services: keycloak-services: Conditional OTP skip-header policy evaluated against untrusted proxy headers
https://bugzilla.redhat.com/show_bug.cgi?id=2539280CVE-2026-96445 - Red Hat Customer Portal
Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a
https://access.redhat.com/security/cve/CVE-2026-96445Vendor Advisories for CVE-2026-96445(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-24 15:09 UTCEG score recompute
- 2026-09-24 15:09 UTCGHSA enrichment
- 2026-09-24 14:04 UTCEPSS rescore
- 2026-09-23 20:23 UTCEG score recompute
- 2026-09-23 20:23 UTCGHSA enrichment
- 2026-09-23 19:53 UTCEG score recompute
- 2026-09-23 19:53 UTCGHSA enrichment
- 2026-09-23 12:30 UTCEG score recompute
- 2026-09-23 11:21 UTCEG score recompute
- 2026-09-23 11:21 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-96445?
When was CVE-2026-96445 disclosed?
Is CVE-2026-96445 actively exploited?
What is the CVSS score of CVE-2026-96445?
How do I remediate CVE-2026-96445?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-96445
Is Your Infrastructure Affected by CVE-2026-96445?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.