CVE-2025-11537: Keycloak logs sensitive headers

CVE-2025-11537 · Severity: medium · CVSS 5 · Published 2026-02-10

A flaw was found in Keycloak. When the logging format is configured to a verbose, user-supplied pattern (such as the pre-defined 'long' pattern), sensitive headers including Authorization and Cookie are disclosed to the logs in cleartext. An attacker with read access to the log files can extract these credentials (e.g., bearer tokens, session cookies) and use them to impersonate users, leading to a full account compromise.

Technologies: org.keycloak:keycloak-quarkus-server (Maven). Vendors: Maven.

Quick answers

Is CVE-2025-11537 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-11537 being exploited in the wild.
How severe is CVE-2025-11537?
Medium severity, with a CVSS score of 5, published 10 February 2026.
Which products and versions are affected?
org.keycloak:keycloak-quarkus-server (Maven) < 26.5.6, ECOSYSTEM:introduced=0,fixed=26.5.6.
Is there a fix for CVE-2025-11537?
Yes. org.keycloak:keycloak-quarkus-server (Maven): upgrade to 26.5.6 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-11537?
Check whether you run org.keycloak:keycloak-quarkus-server (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.keycloak:keycloak-quarkus-server (Maven): upgrade to 26.5.6 or later
    # set org.keycloak:keycloak-quarkus-server to 26.5.6 in your pom.xml or build.gradle

Affected products

  • org.keycloak:keycloak-quarkus-server (Maven) < 26.5.6, ECOSYSTEM:introduced=0,fixed=26.5.6

Identifiers

  • CVE-2025-11537
  • GHSA-gv3v-2cpp-3pmq

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.