CVE-2026-93541

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-09-24. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An out-of-bounds read in libXi's XQueryDeviceState() in libXi before 1.8.4 could be used by a

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

September 24, 2026

Last Modified

September 24, 2026

Advisory Details (1)

Auto-updated Sep 24, 2026
No patch confirmed yet.
generic

Fixes for AISLE reports (!23) · Merge requests · xorg / lib / libXi · GitLab

https://gitlab.freedesktop.org/xorg/lib/libxi/-/merge_requests/23/diffs?commit_id=7b6fffd13fd3914e0b39f3a4f131913da7f066e7

Vendor Advisories for CVE-2026-93541(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 7× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-24 21:01 UTCGHSA enrichment
  2. 2026-09-24 18:36 UTCEG score recompute
  3. 2026-09-24 18:36 UTCGHSA enrichment
  4. 2026-09-24 17:32 UTCEG score recompute
  5. 2026-09-24 16:32 UTCEG score recompute
  6. 2026-09-24 16:02 UTCEG score recompute
  7. 2026-09-24 16:01 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-93541?
CVE-2026-93541 is a medium vulnerability published on September 24, 2026. An out-of-bounds read in libXi's XQueryDeviceState() in libXi before 1.8.4 could be used by a
When was CVE-2026-93541 disclosed?
CVE-2026-93541 was first published in the National Vulnerability Database on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-93541?
CVE-2026-93541 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-93541?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-93541, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-93541

Explore →

Is Your Infrastructure Affected by CVE-2026-93541?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs