CVE-2026-65097

CVE-2026-65097 is a high-severity vulnerability in Nvidia Nemoclaw with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-494.

Key facts

Description

NVIDIA NemoClaw for Linux contains a vulnerability in its installation scripts, where an attacker could cause a download of code without integrity check. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

Frequently asked questions

What is CVE-2026-65097?
NVIDIA NemoClaw for Linux contains a vulnerability in its installation scripts, where an attacker could cause a download of code without integrity check. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.
How severe is CVE-2026-65097?
CVE-2026-65097 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with high attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-65097 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (22nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-65097?
CVE-2026-65097 affects Nvidia Nemoclaw. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-65097?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-65097 published?
CVE-2026-65097 was published on 2026-08-25 and last updated on 2026-09-01.

References

Affected products (1)

More vulnerabilities in Nvidia Nemoclaw

All CVEs affecting Nvidia Nemoclaw →

Other CWE-494 vulnerabilities

Browse all CWE-494 vulnerabilities →