CVE-2024-4028VulnerabilityPublished 18 Feb 2025Updated 21 Nov 2025

CVE-2024-4028: keycloak · Improper Input Validation

Affects keycloakSource CVE Database V5

Not known to be exploited · CVSS 3.8 Low.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

3.8Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 18 Feb 2025
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.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.keycloak/keycloak`pkg:maven/org.keycloak/keycloak`Other threats	Affected =18.0.8	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-4028, organizations should first verify if they are running the affected Keycloak version 18.0.8 and plan to upgrade to a patched version once available. In the absence of an official patch, administrators should restrict access to the Keycloak admin console to trusted personnel only and enforce strict privilege management to limit the number of users with permission creation capabilities. Implementing web application firewalls (WAFs) with rules to detect and block XSS payloads targeting the admin console can provide additional protection. Regularly audit permissions and resource configurations for suspicious entries that may indicate exploitation attempts. Employ Content Security Policy (CSP) headers to reduce the impact of potential XSS attacks by restricting script execution sources. Monitoring and logging administrative actions can help detect anomalous behavior early. Finally, coordinate with Keycloak maintainers and security advisories to apply official patches promptly once released.

Description

A vulnerability was found in Keycloak. This issue may allow a privileged attacker to use a malicious payload as the permission while creating items (Resource and Permissions) from the admin console, leading to a stored cross-site scripting (XSS) attack.

Impact

The primary impact of CVE-2024-4028 is the potential compromise of administrative sessions within Keycloak environments. Successful exploitation could allow an attacker with administrative privileges to execute arbitrary scripts in the context of the admin console, leading to session hijacking, unauthorized changes to identity and access management configurations, or leakage of sensitive information. While the vulnerability requires high privileges, it could facilitate lateral movement or privilege escalation if combined with other vulnerabilities or misconfigurations. Organizations relying on Keycloak for authentication and authorization in critical applications or cloud services may face increased risk of identity compromise, which can cascade into broader system breaches. The low CVSS score reflects limited scope and ease of exploitation, but the impact on confidentiality and integrity in trusted administrative contexts remains significant. No disruption to availability is expected. The lack of known exploits reduces immediate risk, but the vulnerability should be treated seriously due to the sensitive nature of Keycloak's role in security infrastructure.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 21:54 UTC

Technical details

References

Community reviews

Related threats