CVE-2026-34003 | X.org X Server XKB Key Types Request out-of-bounds (EUVD-2026-25231)
VulDBArchived Apr 23, 2026✓ Full text saved
A vulnerability categorized as critical has been discovered in X.org X Server . Affected by this vulnerability is an unknown functionality of the component XKB Key Types Request Handler . Such manipulation leads to out-of-bounds read. This vulnerability is referenced as CVE-2026-34003 . The attack can only be performed from a local environment. No exploit is available.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-359151 · CVE-2026-34003 · EUVD-2026-25231
X.ORG X SERVER XKB KEY TYPES REQUEST OUT-OF-BOUNDS
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.8 $0-$5k 2.08
Summaryinfo
A vulnerability identified as critical has been detected in X.org X Server. Affected by this issue is some unknown functionality of the component XKB Key Types Request Handler. Performing a manipulation results in out-of-bounds. This vulnerability is identified as CVE-2026-34003. The attack is only possible with local access. There is not any exploit available.
Detailsinfo
A vulnerability was found in X.org X Server (affected version not known). It has been classified as critical. This affects some unknown functionality of the component XKB Key Types Request Handler. The manipulation with an unknown input leads to a out-of-bounds vulnerability. CWE is classifying the issue as CWE-125. The product reads data past the end, or before the beginning, of the intended buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at access.redhat.com. This vulnerability is uniquely identified as CVE-2026-34003 since 03/25/2026. The exploitability is told to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-25231).
Productinfo
Vendor
X.org
Name
X Server
License
open-source
Website
Vendor: https://www.x.org/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 7.8
VulDB Meta Temp Score: 7.8
VulDB Base Score: 7.8
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.8
CNA Vector (redhat): 🔒
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Out-of-bounds
CWE: CWE-125 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/25/2026 CVE reserved
04/23/2026 +28 days Advisory disclosed
04/23/2026 +0 days VulDB entry created
04/23/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: x.org
Advisory: access.redhat.com
Status: Confirmed
CVE: CVE-2026-34003 (🔒)
GCVE (CVE): GCVE-0-2026-34003
GCVE (VulDB): GCVE-100-359151
EUVD: 🔒
Entryinfo
Created: 04/23/2026 18:14
Updated: 04/23/2026 19:29
Changes: 04/23/2026 18:14 (61), 04/23/2026 19:29 (1)
Complete: 🔍
Cache ID: 99:845:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸