Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.newCreate a CVE report
Check your stack
CVE-2025-11537

Keycloak-services: sensitive headers shown in the http access logs

Products / packages Red Hat build of Keycloak 26.4.2 · Red Hat Build of Keycloak · org.keycloak:keycloak-quarkus-server

Published

Share

Severity and exploitation

Not in CISA KEVSource: MODERATE

KEV coverage does not rule out exploitation.

KEV checked 14/11/2026, 22:20:30 UTC
redhat · CVSS:3.1 · 5
Assessment vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
OSV · CVSS:3.1 · 5
Assessment vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
The headline uses the highest imported catalog score. Assessments can differ by source and CVSS version.

Severity

medium5.0

CVSS measures technical severity, not the likelihood of an attack.

Known exploitation

Not listed in the checked CISA KEV catalog

Absence from CISA KEV does not rule out attacks.

Public exploit

Not established by this record

Missing evidence does not mean no public exploit exists.

Remediation

Package fixes recorded

Fix versions are recorded for 1 of 1 mapped packages. Check each release branch and any separate product guidance.

What this means

Keycloak has a flaw that discloses sensitive headers, including Authorization and Cookie, to logs in cleartext when the logging format is set to a verbose pattern. An attacker with read access to the log files can extract these credentials. The affected versions are prior to 26.5.6.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Attack conditions

No attack-condition excerpt has been identified here. Review the full source description and references for authentication, network access, and configuration requirements.

Review supporting sources →

Affected versions

Check the exact model, release, and any platform requirements against your installation.

Red Hat · redhat

Red Hat build of Keycloak 26.4.2

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: unaffected

Product identifiers (CPE)cpe:/a:redhat:build_keycloak:26.4::el9

Red Hat · redhat

Red Hat Build of Keycloak

0 ranges
redhat version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

unaffected

unknown

Other versions: affected

Product identifiers (CPE)cpe:/a:redhat:build_keycloak:

Packages

Compare each installed version with the publisher’s affected ranges. Where a fix is recorded, choose the appropriate release branch and test compatibility before upgrading.

What to do

Compare your installed product and version with the affected versions above. A matching product name alone does not confirm exposure.

Use the recorded fix for your release branch. Review the publisher’s instructions and test compatibility before upgrading.

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

redhat guidance ↗

cve.new guidance unless attributed to a publisher. This page does not inspect your installation.

Public exploit evidence

No public exploit reference is identified in the imported evidence. This is not a claim that no exploit exists.

Original source description

Read the full publisher description

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.

Patches are available, see:

References

10 sources
access.redhat.com/errata/RHEA-2025:19385
Vendor advisoryredhat
access.redhat.com/errata/RHEA-2025:19386
Vendor advisoryredhat
access.redhat.com/security/cve/CVE-2025-11537
Security advisoryredhat
bugzilla.redhat.com/show_bug.cgi
Source referenceredhat
nvd.nist.gov/vuln/detail/CVE-2025-11537
Security advisory
keycloak/keycloak · commit 137a35c
Patch
View 4 more references
keycloak/keycloak · commit 5a3cdb7
Patch
keycloak/keycloak · commit 9622f55
Patch
keycloak/keycloak · repository
Source reference
www.keycloak.org/server/logging
Source reference

Inside the record

Evidence available

Package identity
Version evidence
Remediation guidance
Weakness classification
Additional publishers

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2025-11537

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-117 ↗

Improper Output Neutralization for Logs

redhat

Related →
Contributing organizations · 2
redhat

Assigning organization

2026-10-30
CISA-ADP

Additional data publisher

2026-02-10

Timeline

All times UTC

  1. Advisory published

    Publication date supplied by the source.

  2. Source updated

    Latest modification date supplied by the source.

  3. Last imported by cve.new

    Latest catalog import, not the date we first saw this advisory.

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.