| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.3 | $0-$5k | 1.78 |
Summary
A vulnerability, which was classified as problematic, has been found in libinput. This issue affects some unknown processing. The manipulation leads to expired pointer dereference. This vulnerability is uniquely identified as CVE-2026-35094. Local access is required to approach this attack. No exploit exists.
Details
A vulnerability was found in libinput (affected version unknown) and classified as problematic. This issue affects an unknown functionality. The manipulation with an unknown input leads to a expired pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-825. The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid. Impacted is confidentiality. The summary by CVE is:
A flaw was found in libinput. An attacker capable of deploying a Lua plugin file in specific system directories can exploit a dangling pointer vulnerability. This occurs when a garbage collection cleanup function is called, leaving a pointer that can then be printed to system logs. This could potentially expose sensitive data if the memory location is re-used, leading to information disclosure. For this exploit to work, Lua plugins must be enabled in libinput and loaded by the compositor.
The advisory is shared at access.redhat.com. The identification of this vulnerability is CVE-2026-35094 since 04/01/2026. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are 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-17909). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.3VulDB Meta Temp Score: 3.3
VulDB Base Score: 3.3
VulDB Temp Score: 3.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector (redhat): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Expired pointer dereferenceCWE: CWE-825
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
04/01/2026 Advisory disclosed04/01/2026 CVE reserved
04/01/2026 VulDB entry created
04/01/2026 VulDB entry last update
Sources
Advisory: access.redhat.comStatus: Not defined
CVE: CVE-2026-35094 (🔒)
GCVE (CVE): GCVE-0-2026-35094
GCVE (VulDB): GCVE-100-354677
EUVD: 🔒
Entry
Created: 04/01/2026 17:01Updated: 04/01/2026 19:39
Changes: 04/01/2026 17:01 (58), 04/01/2026 19:39 (1)
Complete: 🔍
Cache ID: 216:2DB:103
No comments yet. Languages: en.
Please log in to comment.