Keycloak logs sensitive headers
Moderate severity
GitHub Reviewed
Published
Feb 10, 2026
to the GitHub Advisory Database
•
Updated Mar 4, 2026
Package
Affected versions
< 26.6.0
Patched versions
26.6.0
Description
Published by the National Vulnerability Database
Feb 10, 2026
Published to the GitHub Advisory Database
Feb 10, 2026
Reviewed
Feb 11, 2026
Last updated
Mar 4, 2026
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.
References