Описание
Keycloak logs sensitive headers
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:
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2025-11537
- https://github.com/keycloak/keycloak/commit/137a35c1109ff43a305f26264978a3ea21452373
- https://github.com/keycloak/keycloak/commit/5a3cdb7c4ccbf83ffc926f70d655a60269d7207b
- https://github.com/keycloak/keycloak/commit/9622f550a6e565b29a3a37454421f08626791a6c
- https://access.redhat.com/security/cve/CVE-2025-11537
- https://bugzilla.redhat.com/show_bug.cgi?id=2402616
- https://www.keycloak.org/server/logging#_change_log_formatpattern
Пакеты
org.keycloak:keycloak-quarkus-server
< 26.5.6
26.5.6
Связанные уязвимости
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.
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.
A flaw was found in Keycloak. When the logging format is configured to ...