Skip to main content
VulnerabilityPublished Updated

CVE-2026-96445: Improper Authentication

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-96445· Medium 6.8

Not known to be exploited · CVSS 6.8 Medium : update Red Hat build of Keycloak 26.6.8 when convenient.

Data as of 6 Nov 2026, 14:03 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.16.8
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat build of Keycloak 26.6.8keycloak-servicesAffected–Fixed in–
Red Hat build of Keycloak 26.6.8rhbk/keycloak-rhel9Affected–Fixed in–
Red Hat Single Sign-On 7keycloak-servicesAffected–Fixed in–

AI-suggested

Red Hat has released Keycloak version 26.6.8 containing multiple security fixes. Users should upgrade to this version or later to address known vulnerabilities. Since the vendor advisory does not explicitly state otherwise, applying this official fix is the recommended mitigation. No indication exists that no action is required or that the issue is already mitigated by other means.

Description

A vulnerability in the Conditional OTP authenticator of Keycloak allows bypassing second-factor authentication. The flaw arises because the system does not verify whether certain HTTP headers used to decide OTP skipping originate from trusted sources. An attacker with a user's password could exploit this by crafting headers to bypass the OTP requirement.

References

Community reviews

Loading reviews…