Skip to main content
VulnerabilityPublished Updated

CVE-2025-11537: Org.keycloak:keycloak quarkus server: Keycloak logs sensitive headers

Affects org.keycloak:keycloak-quarkus-serverSource GCVE Database

0
Compare
Authoritative record:CVE-2025-11537· Medium 5.0

Not known to be exploited · CVSS 5.0 Medium : upgrade to 26.5.6 when convenient.

Data as of 30 Oct 2026, 23:51 UTC

CVSS 3.1 base score
5.0Medium
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.15.0
Patch
Available – fixed in 26.5.6
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Feb 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 30 Oct 2026.

What to do

Upgrade org.keycloak:keycloak-quarkus-server to 26.5.6.

Affected software

ProductAffectedFixed in
Mavenorg.keycloak:keycloak-quarkus-serverAffected
  • <26.5.6
Fixed in
  • 26.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Apply the official patches available in Keycloak version 26.5.6 or later. Refer to the Red Hat advisories RHEA-2025:19385 and RHEA-2025:19386 for detailed update instructions. Avoid using verbose user-supplied logging patterns that include sensitive headers until patched. Since a fix is available, updating to a fixed version is the recommended remediation.

Description

A vulnerability in Keycloak Quarkus Server allows sensitive HTTP headers such as Authorization and Cookie to be logged in cleartext when verbose user-supplied logging patterns are used. An attacker with access to these logs could extract credentials like bearer tokens and session cookies, potentially leading to user impersonation and account compromise. Patches addressing this issue are available in Keycloak version 26.5.6 and later.

References

Community reviews

Loading reviews…