CVE-2026-65088 json
NVIDIA NemoClaw contains a vulnerability where an attacker could cause invocation of process using visible sensitive information.
published 2mo ago modified 2mo ago also EUVD-2026-66106
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
NVIDIA NemoClaw contains a vulnerability where an attacker could cause invocation of process using visible sensitive information. A successful exploit of this vulnerability might lead to information disclosure.
Patch / fix
Is CVE-2026-65088 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2mo ago
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- NVIDIA NemoClaw
Classification
- Weakness
-
- CWE-214 Invocation of Process Using Visible Sensitive Information
References
-
github.com
/NVIDIA/product-security/tree/main/2026/5872
patch
-
nvd.nist.gov
/vuln/detail/CVE-2026-65088
us-government-resource
-
cve.org
/CVERecord?id=CVE-2026-65088
third-party-advisory
Sources
- CVE List CVE-2026-65088
- NVD CVE-2026-65088
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.