NVIDIA OpenShell for all platforms contains a vulnerability where a malicious gateway could cause OS command injection. A successful exploit of this vulnerability might lead to code execution, data tampering, and information disclosure.
CVE-2026-65091
Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 8.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(high)
- EG Risk
- 40(Track)EG Risk 40/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 computedSeverity88% × 45%Exploitation1% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 69%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 28, 2026
Advisory Details (2)
Auto-updated Aug 25, 2026product-security/2026/5872 at main · NVIDIA/product-security · GitHub
https://github.com/NVIDIA/product-security/tree/main/2026/5872Vendor Advisories for CVE-2026-65091(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 / 21× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 21:39 UTCGHSA enrichment
- 2026-08-29 08:50 UTCEG score recompute
- 2026-08-29 08:49 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:58 UTCGHSA enrichment
- 2026-08-28 07:13 UTCGHSA enrichment
- 2026-08-28 07:10 UTCGHSA enrichment
- 2026-08-27 18:19 UTCEG score recompute
- 2026-08-27 18:18 UTCGHSA enrichment
- 2026-08-27 05:28 UTCGHSA enrichment
- 2026-08-26 16:37 UTCEG score recompute
- 2026-08-26 16:37 UTCGHSA enrichment
- 2026-08-26 15:57 UTCEG score recompute
- 2026-08-26 15:57 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 10:16 UTCEG score recompute
- 2026-08-26 10:16 UTCGHSA enrichment
- 2026-08-25 21:27 UTCEG score recompute
- 2026-08-25 20:25 UTCEG score recompute
- 2026-08-25 20:25 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-65091?
When was CVE-2026-65091 disclosed?
Is CVE-2026-65091 actively exploited?
What is the CVSS score of CVE-2026-65091?
How do I remediate CVE-2026-65091?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65091
Is Your Infrastructure Affected by CVE-2026-65091?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.