CVE-2025-11537VulnerabilityPublished 10 Feb 2026Updated 4 Sep 2026

CVE-2025-11537: Red Hat Build of Keycloak · Log Injection

Affects Red Hat Build of KeycloakSource CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

cwe-117

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat Build of Keycloak	Affected–	Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately review and adjust their logging configurations to avoid using verbose or user-supplied patterns that log sensitive headers such as Authorization and Cookie. Specifically, disable or modify the 'long' logging pattern or any custom patterns that include sensitive data. Access controls on log files must be strictly enforced to ensure that only authorized personnel can read them, employing least privilege principles. Implement log monitoring and alerting to detect unusual access patterns or attempts to read logs. Consider encrypting log files at rest and in transit to reduce the risk of unauthorized disclosure. Regularly audit logging configurations and access permissions as part of security hygiene. If possible, update to a patched version of Keycloak once available from Red Hat. Additionally, educate administrators and developers about the risks of logging sensitive information and incorporate secure logging practices into development and deployment workflows.

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.

Impact

The primary impact of this vulnerability is the potential disclosure of sensitive authentication credentials through application logs. If an attacker can read the logs, they can extract bearer tokens or session cookies and impersonate users, leading to unauthorized access and full account compromise. This can result in unauthorized data access, privilege escalation, and potential lateral movement within an organization's network. Although the vulnerability does not affect system availability or integrity directly, the confidentiality breach can have severe consequences including data breaches, regulatory non-compliance, and reputational damage. Organizations relying on Keycloak for identity management and authentication are at risk, especially if log files are not adequately protected or if verbose logging is enabled in production environments. The requirement for local or limited privileges to access logs somewhat limits the attack scope, but insider threats or attackers who have gained initial footholds could exploit this vulnerability to escalate access.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 19:07 UTC

Technical details

References

Community reviews

Related threats