VulnerabilityPublished 9 Oct 2024Updated 9 Oct 2026

CVE-2024-3656: Red Hat Build of Keycloak · Information Exposure

Affects Red Hat Build of KeycloakSource CVE Database V5

Not known to be exploited · public detection template (Nuclei) · CVSS 8.1 High : upgrade Red Hat Build of Keycloak to 24.0.5 soon.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.1High

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

EPSS: 3.3% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 24.0.5

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: 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: 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: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 9 Oct 2024
Detectable: evidence found.
nuclei template: Keycloak < 24.0.5 - Broken Access Control
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

Upgrade keycloak to 24.0.5.

Affected software

Product	Affected	Fixed in
GitHubkeycloak`pkg:github/keycloak`Other threats	Affected <24.0.5	Fixed in 24.0.5

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

AI-suggested

Organizations should immediately review and restrict access to Keycloak's administrative REST API endpoints, ensuring that only fully trusted administrators have permissions. Implement network-level controls such as IP whitelisting or VPN access to limit exposure of the admin API. Monitor logs for unusual administrative activity or access patterns indicative of privilege escalation attempts. In the absence of official patches, consider deploying Web Application Firewalls (WAFs) with custom rules to block unauthorized API calls targeting admin endpoints. Conduct thorough audits of user roles and permissions to remove unnecessary privileges and enforce the principle of least privilege. Additionally, enable multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential misuse. Regularly back up Keycloak configurations and user data to enable recovery in case of compromise.

Description

A flaw was found in Keycloak. Certain endpoints in Keycloak's admin REST API allow low-privilege users to access administrative functionalities. This flaw allows users to perform actions reserved for administrators, potentially leading to data breaches or system compromise.

Impact

The vulnerability poses a significant risk to organizations using Keycloak for identity and access management. Unauthorized administrative access can lead to exposure of sensitive user data, credentials, and configuration settings, undermining confidentiality. Integrity is also at risk as attackers could modify user roles, permissions, or system configurations, potentially creating backdoors or persistent access. Although availability is not directly impacted, the resulting compromise could facilitate further attacks that degrade service. Organizations relying on Keycloak for authentication in cloud environments, enterprise applications, or critical infrastructure could face data breaches, compliance violations, and reputational damage. The ease of exploitation over the network with low privileges and no user interaction increases the likelihood of targeted or opportunistic attacks. The absence of known exploits currently provides a window for proactive mitigation, but the threat remains urgent due to the high impact and accessibility of the flaw.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:55 UTC

Public exploits and detectiona Nuclei detection template

Technical details

References

Community reviews

Related threats