Skip to content
Fencer Vulns
medium 6.8

CVE-2026-96445 json

Keycloak-services: keycloak-services: conditional otp skip-header policy evaluated against untrusted proxy headers

published 2026-09-23 47 d ago modified 2026-11-06 3 d ago also EUVD-2026-85223

cvss
6.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 40%
public exploits
0
none known

Summary

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.

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-96445 updated cvss 6.8

keycloak-services: keycloak-services: Conditional OTP skip-header policy evaluated against untrusted proxy headers

  • Red Hat build of Keycloak 26.6.8
    fixed: vendor fix RHSA-2026:95761
  • Red Hat Single Sign-On 7 keycloak-services 18.0.19.redhat-00002
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
46 d ago

Exploit prediction

0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.8 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Red Hat Red Hat build of Keycloak 26.6.8
  • Red Hat Red Hat Single Sign-On 7

Classification

Weakness

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.