CVE-2025-10939VulnerabilityPublished 28 Oct 2025Updated 19 Dec 2025

CVE-2025-10939: Red Hat build of Keycloak 26.4 · Uncontrolled Search Path Element

Affects Red Hat build of Keycloak 26.4Source CVE Database V5

Not known to be exploited · CVSS 3.7 Low.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

3.7Low

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

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

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
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: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: 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 28 Oct 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-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

AI-suggested

To mitigate CVE-2025-10939, European organizations should implement the following specific measures: 1) Review and harden proxy configurations, especially HAProxy, to enforce strict path normalization and reject relative or non-normalized URL paths that could be exploited to access restricted endpoints. 2) Explicitly block external access to the /admin path on proxies and firewalls, ensuring it is only accessible from trusted internal networks. 3) Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious path traversal or manipulation attempts targeting Keycloak endpoints. 4) Monitor access logs for unusual requests attempting to access /admin via indirect paths and investigate anomalies promptly. 5) Keep Keycloak and proxy software up to date with the latest security patches and advisories from Red Hat and proxy vendors. 6) Conduct regular security assessments and penetration tests focusing on proxy configurations and identity management interfaces to detect similar path-related vulnerabilities. 7) Educate system administrators on secure proxy deployment best practices and the importance of adhering to Keycloak's security guidelines regarding path exposure. These targeted actions go beyond generic advice by focusing on proxy path handling and access control specific to this vulnerability.

Description

CVE-2025-10939 is a low-severity vulnerability in the Red Hat build of Keycloak 26.4 involving an uncontrolled search path element. The issue arises when a proxy, such as HAProxy, is used and relative or non-normalized paths can be exploited to access the /admin path, which is recommended to be blocked from external exposure. This flaw could allow unauthorized users to reach administrative interfaces indirectly via the /realms path, potentially bypassing intended access restrictions. The vulnerability does not require authentication or user interaction but has a low impact limited to confidentiality with no integrity or availability effects. No known exploits are currently reported in the wild. European organizations using Keycloak behind proxies should review their proxy configurations to ensure strict path normalization and access controls. Countries with significant Red Hat and Keycloak adoption, especially those with critical identity management infrastructures, are more likely to be affected. Given the low CVSS score (3.7) and the nature of the flaw, the overall risk is low but warrants attention to prevent potential reconnaissance or limited information disclosure.

Impact

For European organizations, the primary impact of CVE-2025-10939 lies in potential unauthorized access to administrative interfaces of Keycloak deployments, which could lead to information disclosure about the identity management system's configuration or administrative functions. While the vulnerability does not directly allow modification or denial of service, exposure of the /admin path could facilitate further reconnaissance or targeted attacks against identity infrastructure. Organizations relying on Keycloak for authentication and authorization services may face increased risk if proxy configurations are not hardened, potentially compromising the confidentiality of sensitive identity management data. The impact is more pronounced in sectors with stringent identity and access management requirements, such as finance, healthcare, and government institutions. However, given the low severity and absence of known exploits, the immediate risk is limited but should not be ignored. Failure to address this vulnerability could undermine trust in identity services and complicate compliance with data protection regulations like GDPR if sensitive administrative information is leaked.

Summary

CVE-2025-10939 identifies a vulnerability in the Red Hat build of Keycloak version 26.4 related to an uncontrolled search path element when deployed behind certain proxies, notably HAProxy. Keycloak's official guidance advises against exposing the /admin path externally when using a proxy to prevent unauthorized access. However, this vulnerability allows an attacker to exploit relative or non-normalized URL paths to circumvent these restrictions. Specifically, HAProxy can be tricked into resolving paths relative to /realms, which is typically exposed, thereby enabling indirect access to the /admin interface. This flaw stems from insufficient path normalization and validation in the proxy configuration or Keycloak's handling of proxied requests. The vulnerability does not require any privileges or user interaction, making it remotely exploitable over the network. The impact is limited to confidentiality, as unauthorized access to the admin path could reveal sensitive administrative interfaces or information, but it does not allow modification or disruption of services. The CVSS v3.1 score is 3.7 (low), reflecting the limited impact and the requirement for a complex attack vector involving proxy misconfiguration. No patches or known exploits are currently documented, but the issue highlights the importance of secure proxy setups and strict path normalization to prevent unauthorized access to administrative endpoints in identity management systems like Keycloak.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 19 Dec 2025, 20:49 UTC

Technical details

References

Community reviews

Related threats