VulnerabilityPublished 3 Jun 2024Updated 9 Oct 2026

CVE-2024-4540: Red Hat build of Keycloak 22 · Cleartext Storage of Sensitive Information

Affects Red Hat build of Keycloak 22Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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 3 Jun 2024
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 26 Oct 2026.

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 or the CVSS exploit maturity 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.

What to do

Affected software

Product	Affected	Fixed in
Red HatRed Hat Build of Keycloak	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 22	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 22	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 22	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 24	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 24	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-4540, organizations should first apply any available patches or updates from Keycloak that address the issue. If patches are not yet available, administrators should consider disabling or restricting the use of OAuth 2.0 Pushed Authorization Requests (PAR) or the request_uri authorization request flow until a fix is deployed. Implementing strict cookie security attributes such as Secure, HttpOnly, and SameSite can reduce the risk of cookie interception or cross-site attacks. Network-level protections like TLS enforcement and monitoring for unusual cookie transmissions can help detect exploitation attempts. Additionally, reviewing and minimizing the sensitive data included in client parameters and cookies can reduce exposure. Organizations should also audit their Keycloak configurations and logs for suspicious activity related to authorization requests. Finally, educating developers and security teams about secure OAuth implementations and the risks of cleartext storage of sensitive data is essential to prevent similar issues.

Description

A flaw was found in Keycloak in OAuth 2.0 Pushed Authorization Requests (PAR). Client-provided parameters were found to be included in plain text in the KC_RESTART cookie returned by the authorization server's HTTP response to a `request_uri` authorization request, possibly leading to an information disclosure vulnerability.

Impact

The primary impact of CVE-2024-4540 is the unauthorized disclosure of sensitive OAuth 2.0 parameters, which may include client identifiers, scopes, or other authorization details. Such information leakage can facilitate further attacks such as session hijacking, replay attacks, or targeted phishing by revealing internal authorization details. Organizations relying on Keycloak for identity and access management may face increased risk of data breaches or unauthorized access if attackers intercept these cookies. The vulnerability undermines the confidentiality of the OAuth authorization process, potentially exposing sensitive client data to network attackers or malicious insiders with access to client devices or network traffic. While the vulnerability does not directly affect system integrity or availability, the loss of confidentiality can have cascading effects on trust and security posture. This is particularly critical for organizations handling sensitive user data, financial information, or operating in regulated industries.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 18:27 UTC

Technical details

References

Community reviews

Related threats