Skip to main content
CVE-2026-97846VulnerabilityPublished Updated

Bundesamt für Sicherheit in der Informationstechnik Open Source · Keycloak: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen

Affects Bundesamt für Sicherheit in der Informationstechnik Open SourceSource GCVE Database

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

Not known to be exploited · CVSS 6.8 Medium.

Data as of 9 Nov 2026, 13: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 25 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 9 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

No effective mitigation is currently available that meets Red Hat's criteria for ease of use, deployment, applicability, or stability. Users should monitor Red Hat advisories for updates and consider restricting client credential exposure.

Description

A vulnerability in Keycloak's Standard Token Exchange V2 feature allows bypassing mTLS holder-of-key binding, enabling attackers with stolen client credentials to obtain unrestricted tokens. Exploitation requires valid client credentials and specific non-default configurations. The flaw is due to missing enforcement of client certificate checks in the token exchange process.

References

Community reviews

Loading reviews…