CVE-2024-10492VulnerabilityPublished 25 Nov 2024Updated 13 Oct 2026

CVE-2024-10492: Red Hat build of Keycloak 24 · External Control of File Name or Path

Affects Red Hat build of Keycloak 24Source CVE Database V5

Not known to be exploited · CVSS 2.7 Low : upgrade to 26.0.6 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score

2.7Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: 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: 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 25 Nov 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 2026-10-26.

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

Upgrade keycloak to 26.0.6.

Affected software

Product	Affected	Fixed in
Red HatRed Hat build of Keycloak 24	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 24	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 24.0.9	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.0	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.0	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.0	Affected–	Fixed in–
Red HatRed Hat build of Keycloak 26.0.6	Affected–	Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform 8	Affected–	Fixed in–
Red HatRed Hat JBoss Enterprise Application Platform Expansion Pack	Affected–	Fixed in–
Red HatRed Hat Single Sign-On 7	Affected–	Fixed in–
GitHubkeycloak`pkg:github/keycloak`Other threats	Affected <26.0.6	Fixed in 26.0.6

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

AI-suggested

Red Hat has released updated packages for Red Hat build of Keycloak 24.0.9 that fix this vulnerability. Users should apply these official security updates as provided in Red Hat advisories RHSA-2024:10175 and RHSA-2024:10176. Before updating, back up existing installations including configurations and databases. No additional mitigation is required beyond applying the vendor-provided patches.

Description

A vulnerability was found in Keycloak. A user with high privileges could read sensitive information from a Vault file that is not within the expected context. This attacker must have previous high access to the Keycloak server in order to perform resource creation, for example, an LDAP provider configuration and set up a Vault read file, which will only inform whether that file exists or not.

Impact

The impact is limited to information disclosure of Vault files outside the expected context, requiring prior high privileges on the Keycloak server. There is no indication of integrity or availability impact. The vulnerability allows an attacker to determine the existence of files but does not provide broader access or control. Given the prerequisite of high privileges, the risk is reduced to scenarios where an attacker has already compromised administrative access.

Summary

This vulnerability in Keycloak involves external control of file name or path, enabling a privileged user to read sensitive Vault files not intended to be accessible. The attacker must already have high privileges on the Keycloak server to perform resource creation that triggers the vulnerability, such as configuring an LDAP provider and setting up a Vault read file. The vulnerability is classified as a path traversal issue and has a CVSS 3.0 base score of 2.7 (low severity). Red Hat advisories confirm that fixed packages for Red Hat build of Keycloak 24.0.9 are available, addressing this vulnerability along with other security issues.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Aug 2026, 18:04 UTC

Technical details

References

Community reviews

Related threats