NVIDIA NemoClaw CVE-2026-65098

Exploitation requires network reachability to the NemoClaw remote-access helper workflow on a Linux host running an affected version (0 through 0.0.4); the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates no authentication, no user interaction, and low complexity against a default-reachable helper. The primary limiting factors are the narrow affected-product scope (only deployments actually running NVIDIA NemoClaw), the requirement that the remote-access helper be network-exposed rather than firewalled off, and the current absence of public exploit code, which raises the effort to develop a working attack.

The signals partially conflict and should be weighed together rather than trusting the headline number. The CVSS vector (AV:N/AC:L/PR:N/UI:N) describes a trivially reachable, unauthenticated, low-complexity network attack with total technical impact - CISA's SSVC likewise rates Technical Impact as 'total.' However, SSVC records Exploitation as 'none' and Automatable as 'no,' EPSS sits at only 0.57% (45th percentile), there is no CISA KEV listing, and no public proof-of-concept, which together indicate this is not yet a mass-exploited or wormable threat. The practical read is that NemoClaw's niche deployment footprint, not any technical mitigation, is what keeps real-world risk lower than the 9.8 implies; any organization that actually runs NemoClaw should still treat it as a high-priority patch because the exploitation prerequisites are minimal once the product is exposed.

An attacker who can reach a NemoClaw host over the network connects to the remote-access helper endpoint and defeats its weak authentication without valid credentials, then leverages that access to run code, read sensitive data, or alter files on the Linux system. No user interaction or prior privileges are required per the CVSS vector, though no public exploit code is currently available to lower the effort.