CVE-2026-94286

HIGHPre-NVD 7.17.1—
EchelonGraph scoreHIGH confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-28. A secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.1Exploit: None knownExposed services: Not assessed

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

An out-of-bounds read in libXtst's RECORD reply parser in libXtst before 1.2.6 could be used by malicious X servers to crash attached X clients.

CVSS v3
7.1
EG Score
7.1HIGHhigh confidence
EG Risk
32
EG Risk 32/100CISA SSVC

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
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
7th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (1)

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

parse_reply_call_callback: check element size against remaining reply buffer (!10) · Merge requests · xorg / lib / libXtst · GitLab

https://gitlab.freedesktop.org/xorg/lib/libxtst/-/merge_requests/10/diffs?commit_id=16023c86070e6af9407330deea3938fcef75815b

Vendor Advisories for CVE-2026-94286(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libxtst2:1.2.3-1.1, 2:1.2.5-1
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libxtst2:1.2.5-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libxtst2:1.2.5-1
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 45× in last 7d / 49× 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-10-05 07:23 UTCEG score recompute
  2. 2026-10-05 07:23 UTCVendor advisory
  3. 2026-10-05 07:23 UTCGHSA enrichment
  4. 2026-10-04 23:23 UTCEPSS rescore
  5. 2026-10-04 18:44 UTCVendor advisory
  6. 2026-10-04 18:43 UTCGHSA enrichment
  7. 2026-10-04 06:00 UTCVendor advisory
  8. 2026-10-04 06:00 UTCGHSA enrichment
  9. 2026-10-03 17:22 UTCEG score recompute
  10. 2026-10-03 17:22 UTCVendor advisory
  11. 2026-10-03 17:22 UTCGHSA enrichment
  12. 2026-10-03 14:26 UTCEPSS rescore
  13. 2026-10-03 04:43 UTCEG score recompute
  14. 2026-10-03 04:43 UTCVendor advisory
  15. 2026-10-03 04:43 UTCGHSA enrichment
  16. 2026-10-02 17:57 UTCEPSS rescore
  17. 2026-10-02 16:01 UTCVendor advisory
  18. 2026-10-02 16:01 UTCGHSA enrichment
  19. 2026-10-02 03:21 UTCEG score recompute
  20. 2026-10-02 03:21 UTCVendor advisory
  21. 2026-10-02 03:21 UTCGHSA enrichment
  22. 2026-10-01 19:51 UTCEPSS rescore
  23. 2026-10-01 14:42 UTCVendor advisory
  24. 2026-10-01 14:42 UTCGHSA enrichment
  25. 2026-10-01 02:04 UTCEG score recompute
Show 24 more
  1. 2026-10-01 02:04 UTCVendor advisory
  2. 2026-10-01 02:03 UTCGHSA enrichment
  3. 2026-09-30 15:04 UTCEPSS rescore
  4. 2026-09-30 13:24 UTCEG score recompute
  5. 2026-09-30 13:24 UTCVendor advisory
  6. 2026-09-30 13:23 UTCGHSA enrichment
  7. 2026-09-30 13:13 UTCEG score recompute
  8. 2026-09-30 13:13 UTCVendor advisory
  9. 2026-09-30 13:13 UTCGHSA enrichment
  10. 2026-09-30 10:52 UTCVendor advisory
  11. 2026-09-30 10:51 UTCGHSA enrichment
  12. 2026-09-29 22:11 UTCEG score recompute
  13. 2026-09-29 22:11 UTCVendor advisory
  14. 2026-09-29 22:11 UTCGHSA enrichment
  15. 2026-09-29 10:52 UTCVendor advisory
  16. 2026-09-29 10:52 UTCGHSA enrichment
  17. 2026-09-28 22:14 UTCEG score recompute
  18. 2026-09-28 22:13 UTCGHSA enrichment
  19. 2026-09-28 13:52 UTCEPSS rescore
  20. 2026-09-28 13:52 UTCEPSS rescore
  21. 2026-09-28 09:32 UTCEG score recompute
  22. 2026-09-28 09:32 UTCGHSA enrichment
  23. 2026-09-28 08:57 UTCEG score recompute
  24. 2026-09-28 08:57 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-94286?
CVE-2026-94286 is a high vulnerability published on September 28, 2026. An out-of-bounds read in libXtst's RECORD reply parser in libXtst before 1.2.6 could be used by malicious X servers to crash attached X clients.
When was CVE-2026-94286 disclosed?
CVE-2026-94286 was first published on September 28, 2026, with the most recent update on September 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-94286 actively exploited?
CVE-2026-94286 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-94286?
CVE-2026-94286 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-94286?
No fix for CVE-2026-94286 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-94286 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-94286

Explore →

Is Your Infrastructure Affected by CVE-2026-94286?

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

Book a Demo →Browse All CVEs