Red Hat, Inc.

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability. It refers to the loss of availability of the impacted component itself, such as a networked service (e.g., web, database, email). Since availability refers to the accessibility of information resources, attacks that consume network bandwidth, processor cycles, or disk space all impact the availability of an impacted component.

Availability

There is no impact to availability within the impacted component.

None

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability. Such conditions may require the collection of more information about the target or computational exceptions. The assessment of this metric excludes any requirements for user interaction in order to exploit the vulnerability. If a specific configuration is required for an attack to succeed, the Base metrics should be scored assuming the vulnerable component is in that configuration.

Attack Complexity

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.

This metric reflects the context by which vulnerability exploitation is possible. The Base Score increases the more remote (logically, and physically) an attacker can be in order to exploit the vulnerable component.

Attack Vector

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).

Network

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability. Confidentiality refers to limiting information access and disclosure to only authorized users, as well as preventing access by, or disclosure to, unauthorized ones.

Confidentiality

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.

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

Integrity

There is no loss of integrity within the impacted component.

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Privileges Required

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.

High

Does a successful attack impact a component other than the vulnerable component? If so, the Base Score increases and the Confidentiality, Integrity and Authentication metrics should be scored relative to the impacted component.

Scope

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.

Unchanged

This metric captures the requirement for a user, other than the attacker, to participate in the successful compromise the vulnerable component. This metric determines whether the vulnerability can be exploited solely at the will of the attacker, or whether a separate user (or user-initiated process) must participate in some manner.

User Interaction

The vulnerable system can be exploited without any interaction from any user.

Metasploit Framework

ProjectDiscovery nuclei-templates

Exploit-DB

CVE Program CNA list

FIRST CVSS v3.1

FIRST CVSS v4.0

CVE-2025-10043 is a vulnerability affecting the Red Hat build of Keycloak version 26.2, an open-source identity and access management solution widely used for single sign-on and authentication services. The vulnerability is characterized by a CVSS 3.1 vector indicating network attack vector (AV:N), low attack complexity (AC:L), requiring high privileges (PR:H), no user interaction (UI:N), unchanged scope (S:U), and limited confidentiality impact (C:L) with no impact on integrity (I:N) or availability (A:N). This suggests that an authenticated attacker with elevated privileges can remotely exploit the vulnerability to gain limited unauthorized access to confidential information. The absence of known exploits or patches at the time of publication indicates that the vulnerability is newly disclosed and may require further analysis and mitigation. The lack of detailed technical information and CWE classification limits the ability to fully understand the exploitation mechanism, but the requirement for high privileges reduces the risk of widespread exploitation. Keycloak's role as an identity provider means that any confidentiality breach could expose sensitive authentication data or configuration details, potentially aiding further attacks if combined with other vulnerabilities.

CVE Database V5

Detailed information about CVE-2025-10043: External Control of File Name or Path in Red Hat Red Hat Build of Keycloak affecting Red Hat Red Hat Build of Keycloa

CVE-2025-10043 has been rejected

Official rejection reason