Local service interruption via write-path unsigned underflow
Published Sep 28, 2026 · Updated Sep 28, 2026
Unsigned underflow in the X.Org libXpm write path before 3.5.19 allows local users to exhaust CPU and memory during XPM output. Public material does not identify the write-path function, the subtraction that wraps, or the input that triggers it. Exploitation requires a local path into an application that writes XPM data; the reported consequence is resource exhaustion, not data access or code execution.
Summary
What happened
Unsigned underflow in the X.Org libXpm write path before 3.5.19 allows local users to exhaust CPU and memory during XPM output. Public material does not identify the write-path function, the subtraction that wraps, or the input that triggers it. Exploitation requires a local path into an application that writes XPM data; the reported consequence is resource exhaustion, not data access or code execution.
The record
- CVE
- CVE-2026-94287
- Published
- Sep 28, 2026
- Updated
- Sep 28, 2026
- Vendor
- The X11 Project
- Product
- libXpm
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 28, 2026CVE publishedPublication date reported by the CVE source.
- Sep 28, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <3.5.19
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started