CVE-2026-95182

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-10-16. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-102903 (ENISA EUVD) · GHSA-g5wx-c65h-w9px (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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

An untrusted search path in DeepSeek Harness (dsh) commit c291e796 allows attackers to execute arbitrary code via supplying and opening crafted executable files in place of legitimate content.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
76
EG Risk 76/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
45th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 16, 2026

Last Modified

October 16, 2026

Advisory Details (3)

Auto-updated Oct 31, 2026
No fix on record yet.
Web page

poc/CVE-2026-95182 at main · lkloliver/poc · GitHub

https://github.com/lkloliver/poc/tree/main/CVE-2026-95182
Web page

gist:46a88c7d619e487327a1122c20ff8e32 · GitHub

https://gist.github.com/lkloliver/46a88c7d619e487327a1122c20ff8e32
Web page

DeepSeek | 深度求索

http://deepseek.com

Vendor Advisories for CVE-2026-95182(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 21× in last 7d / 52× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  2. 2026-10-30 13:03 UTCEG score recompute
  3. 2026-10-30 13:03 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-29 13:43 UTCEG score recompute
  6. 2026-10-29 13:43 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  8. 2026-10-28 14:19 UTCEG score recompute
  9. 2026-10-28 14:19 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  10. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-10-27 14:40 UTCEG score recompute
  12. 2026-10-27 14:39 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  13. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-26 15:15 UTCEG score recompute
  15. 2026-10-26 15:14 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  16. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-25 14:54 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  18. 2026-10-25 13:49 UTCEG score recompute
  19. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-24 15:32 UTCEG score recompute
  21. 2026-10-24 15:32 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  22. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-23 16:12 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  24. 2026-10-22 16:45 UTCEG score recompute
  25. 2026-10-22 16:45 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
Show 27 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-10-21 17:24 UTCEG score recompute
  3. 2026-10-21 17:24 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  4. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  5. 2026-10-20 17:36 UTCEG score recompute
  6. 2026-10-20 17:36 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  7. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-19 18:14 UTCEG score recompute
  9. 2026-10-19 18:13 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  10. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-18 18:51 UTCEG score recompute
  12. 2026-10-18 18:50 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  13. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  14. 2026-10-18 02:58 UTCEG score recompute
  15. 2026-10-17 19:30 UTCEG score recompute
  16. 2026-10-17 19:30 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  17. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-16 20:07 UTCEG score recompute
  19. 2026-10-16 20:06 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px · GitHub severity CRITICAL · GitHub CVSS 10.0
  20. 2026-10-16 16:35 UTCEG score recomputeFirst assessed: 10.0 CRITICAL
  21. 2026-10-16 16:35 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px
  22. 2026-10-16 16:30 UTCNVD updateCVSS v3 → 10 · severity → CRITICAL
  23. 2026-10-16 16:03 UTCEG score recompute
  24. 2026-10-16 16:02 UTCGHSA enrichmentGHSA-g5wx-c65h-w9px
  25. 2026-10-16 15:26 UTCNVD update
  26. 2026-10-16 14:49 UTCEG score recompute
  27. 2026-10-16 14:47 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-95182?
CVE-2026-95182 is a critical-severity vulnerability; its CVE record was published on October 16, 2026. An untrusted search path in DeepSeek Harness (dsh) commit c291e796 allows attackers to execute arbitrary code via supplying and opening crafted executable files in place of legitimate content.
When was the CVE record for CVE-2026-95182 published?
The CVE record for CVE-2026-95182 was published on October 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-95182 actively exploited?
CVE-2026-95182 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-95182?
CVE-2026-95182 has a CVSS v3.1 base score of 10.0 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-95182?
No fix for CVE-2026-95182 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-95182 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-95182?

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