Multiple integer overflows in X.org libXi 1.7.1 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overfl
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 78.5% of all records.
- Fixed version: libxi (Debian:12) 2:1.6.1-1+deb7u1; libxi (Debian:6.0) 2:1.3-8; libXi (openSUSE:Tumbleweed) 1.7.8-1.1.
Low priority for now. Upgrade to libxi (Debian:12) 2:1.6.1-1+deb7u1; libxi (Debian:6.0) 2:1.3-8; libXi (openSUSE:Tumbleweed) 1.7.8-1.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple integer overflows in X.org libXi 1.7.1 and earlier allow X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to the (1) XGetDeviceControl, (2) XGetFeedbackControl, (3) XGetDeviceDontPropagateList, (4) XGetDeviceMotionEvents, (5) XIGetProperty, (6) XIGetSelectedEvents, (7) XGetDeviceProperties, and (8) XListInputDevices functions.
- Published
- Jun 15, 2013
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 78th percentile
- CWE
- CWE-189
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| x.org | libxi | cpe:2.3:a:x.org:libxi |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- x.org libxiup to 1.7.1 inclusive
- x.org libxi1.5.0
- x.org libxi1.5.99.2
- x.org libxi1.5.99.3
- x.org libxi1.6.0
- x.org libxi1.6.1
- x.org libxi1.6.2
- x.org libxi1.6.99.1
- x.org libxi1.7
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libxi | before 2:1.6.1-1+deb7u1 | 2:1.6.1-1+deb7u1 |
| Debian:6.0 | libxi | before 2:1.3-8 | 2:1.3-8 |
| openSUSE:Tumbleweed | libXi | before 1.7.8-1.1 | 1.7.8-1.1 |
| Red Hat:enterprise_linux:6::client | libdmx | before 0:1.1.3-3.el6 | 0:1.1.3-3.el6 |
| Red Hat:enterprise_linux:6::client | libdmx-debuginfo | before 0:1.1.3-3.el6 | 0:1.1.3-3.el6 |
| Red Hat:enterprise_linux:6::client | libdmx-devel | before 0:1.1.3-3.el6 | 0:1.1.3-3.el6 |
| Red Hat:enterprise_linux:6::client | libX11 | before 0:1.6.0-2.2.el6 | 0:1.6.0-2.2.el6 |
| Red Hat:enterprise_linux:6::client | libX11-common | before 0:1.6.0-2.2.el6 | 0:1.6.0-2.2.el6 |
| Red Hat:enterprise_linux:6::client | libX11-debuginfo | before 0:1.6.0-2.2.el6 | 0:1.6.0-2.2.el6 |
| Red Hat:enterprise_linux:6::client | libX11-devel | before 0:1.6.0-2.2.el6 | 0:1.6.0-2.2.el6 |
| Red Hat:enterprise_linux:6::client | libxcb | before 0:1.9.1-2.el6 | 0:1.9.1-2.el6 |
| Red Hat:enterprise_linux:6::client | libxcb-debuginfo | before 0:1.9.1-2.el6 | 0:1.9.1-2.el6 |
| Red Hat:enterprise_linux:6::client | libxcb-devel | before 0:1.9.1-2.el6 | 0:1.9.1-2.el6 |
| Red Hat:enterprise_linux:6::client | libxcb-doc | before 0:1.9.1-2.el6 | 0:1.9.1-2.el6 |
| Red Hat:enterprise_linux:6::client | libxcb-python | before 0:1.9.1-2.el6 | 0:1.9.1-2.el6 |
| Red Hat:enterprise_linux:6::client | libXcursor | before 0:1.1.14-2.1.el6 | 0:1.1.14-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXcursor-debuginfo | before 0:1.1.14-2.1.el6 | 0:1.1.14-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXcursor-devel | before 0:1.1.14-2.1.el6 | 0:1.1.14-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXext | before 0:1.3.2-2.1.el6 | 0:1.3.2-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXext-debuginfo | before 0:1.3.2-2.1.el6 | 0:1.3.2-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXext-devel | before 0:1.3.2-2.1.el6 | 0:1.3.2-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXfixes | before 0:5.0.1-2.1.el6 | 0:5.0.1-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXfixes-debuginfo | before 0:5.0.1-2.1.el6 | 0:5.0.1-2.1.el6 |
| Red Hat:enterprise_linux:6::client | libXfixes-devel | before 0:5.0.1-2.1.el6 | 0:5.0.1-2.1.el6 |
+41
Same product
x.org: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-7946X.org libXi before 1.7.7 allows remote X servers to cause a denial of service (infinite loop) via vectors involving length fields.31Monitor
- CVE-2016-7945Multiple integer overflows in X.org libXi before 1.7.7 allow remote X servers to cause a denial of service (out-of-bounds memory access or i31Monitor
- CVE-2026-93543Out-of-bounds read in libXi's XI2 class parser29Monitor
Published before and after this one in the same product
- Later →CVE-2013-1995Jun 15, 2013 · X.org libXi 1.7.1 and earlier allows X servers to trigger allocation of insufficient memory and a buffer overflow via vectors related to an 28Monitor
- Later →CVE-2013-1998Jun 15, 2013 · Multiple buffer overflows in X.org libXi 1.7.1 and earlier allow X servers to cause a denial of service (crash) and possibly execute arbitra28Monitor
- Later →CVE-2026-93541Sep 24, 2026 · Out-of-bounds read in libXi's XQueryDeviceState()26Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libxi | 2:1.6.1-1+deb7u1 · Debian:12 | Package registry (OSV) |
| opensuse:libXi | 1.7.8-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:libX11-debuginfo | 0:1.6.0-2.2.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libX11-devel | 0:1.6.0-2.2.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXcursor-debuginfo | 0:1.1.14-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXcursor-devel | 0:1.1.14-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXext-debuginfo | 0:1.3.2-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXext-devel | 0:1.3.2-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXfixes-debuginfo | 0:5.0.1-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXfixes-devel | 0:5.0.1-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXi-debuginfo | 0:1.7.2-2.2.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXi-devel | 0:1.7.2-2.2.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXinerama-debuginfo | 0:1.1.3-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:libXinerama-devel | 0:1.1.3-2.1.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.