NVIDIA NemoClaw for Linux contains a vulnerability in its migration command, where a local attacker could cause code injection. A successful exploit of this vulnerability might lead to code execution, data tampering, information disclosure, and denial of service.
CVE-2026-65082
Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 7.0; 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
- 7.0
- EG Score
- 7.0(high)
- EG Risk
- 32(Track)EG Risk 32/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 computedSeverity70% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- 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-65082(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 19:09 UTCGHSA enrichment
- 2026-08-29 07:34 UTCEG score recompute
- 2026-08-29 07:34 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-28 19:58 UTCGHSA enrichment
- 2026-08-28 18:54 UTCGHSA enrichment
- 2026-08-28 07:19 UTCGHSA enrichment
- 2026-08-27 19:41 UTCEG score recompute
- 2026-08-27 19:41 UTCGHSA enrichment
- 2026-08-27 08:06 UTCGHSA enrichment
- 2026-08-26 20:30 UTCEG score recompute
- 2026-08-26 20:30 UTCGHSA enrichment
- 2026-08-26 19:28 UTCEG score recompute
- 2026-08-26 19:28 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 09:01 UTCEG score recompute
- 2026-08-26 09:01 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-94
- CVE-2003-1432EG 10.0EPSS p94HIGH
- CVE-2002-0495EG 10.0EPSS p96HIGH
- CVE-1999-0702EG 10.0EPSS p98HIGH
- CVE-1999-0509EG 10.0EPSS p98HIGH
- CVE-2006-1318EG 9.3EPSS p97HIGH
- CVE-2006-1301EG 9.3EPSS p95HIGH
- CVE-2006-1308EG 9.3EPSS p95HIGH
- CVE-2006-1309EG 9.3EPSS p95HIGH
- CVE-2006-1304EG 9.3EPSS p96HIGH
- CVE-2006-1306EG 9.3EPSS p95HIGH
Frequently asked(5)
What is CVE-2026-65082?
When was CVE-2026-65082 disclosed?
Is CVE-2026-65082 actively exploited?
What is the CVSS score of CVE-2026-65082?
How do I remediate CVE-2026-65082?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-65082
Is Your Infrastructure Affected by CVE-2026-65082?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.