CVE-2026-34003 : 상세 정보

CVE-2026-34003

7.8
/
높음
0.01%V4
2026-04-23
14h54 +00:00
Overflow
Local
2026-11-04
22h25 +00:00
특정 CVE 알림
특정 CVE의 변경 사항에 대한 정보를 받아보세요.
알림 관리

CVE 설명

Xorg: xwayland: x.org x server: information exposure and denial of service via out-of-bounds memory access

A flaw was found in the X.Org X server's XKB key types request validation. A local attacker could send a specially crafted request to the X server, leading to an out-of-bounds memory access vulnerability. This could result in the disclosure of sensitive information or cause the server to crash, leading to a Denial of Service (DoS). In certain configurations, higher impact outcomes may be possible.

CVE 정보

관련 약점

CWE-ID 약점 이름 출처
CWE-125 Out-of-bounds Read
The product reads data past the end, or before the beginning, of the intended buffer.

메트릭

메트릭 점수 심각도 CVSS 벡터 출처
V3.1 7.8 HIGH CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

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

Privileges Required

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

Low

The attacker 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 has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

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

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

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.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a 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. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

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

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 Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

High

There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

EPSS

EPSS는 취약점이 악용될 가능성을 예측하는 점수 모델입니다.

EPSS 점수

EPSS 모델은 0과 1(0~100%) 사이의 확률 점수를 생성합니다. 점수가 높을수록 취약점이 악용될 가능성이 높습니다.

EPSS 백분위수

백분위수는 EPSS 점수에 따라 CVE의 순위를 매기는 데 사용됩니다. 예를 들어 EPSS 점수 기준 95번째 백분위수의 CVE는 다른 CVE의 95%보다 악용될 가능성이 높습니다.

참고 자료

https://access.redhat.com/errata/RHSA-2026:10739
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:11352
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:11369
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:11388
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:11656
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:11692
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:13414
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:19125
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:19342
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:19343
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:19344
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20547
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20555
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20557
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20558
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20560
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20561
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20562
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20563
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20575
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20576
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:20590
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21699
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21712
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21715
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21716
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21718
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21741
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:21742
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:22424
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:22456
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:23254
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:23255
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:23496
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/errata/RHSA-2026:24341
Tags : vendor-advisory, x_refsource_REDHAT
https://access.redhat.com/security/cve/CVE-2026-34003
Tags : vdb-entry, x_refsource_REDHAT
https://bugzilla.redhat.com/show_bug.cgi?id=2451113
Tags : issue-tracking, x_refsource_REDHAT