CVE-2026-65097: NVIDIA NemoClaw RCE Vulnerability

CVE-2026-65097 Overview

NVIDIA NemoClaw for Linux contains a vulnerability in its installation scripts that allows attackers to cause a download of code without an integrity check. The flaw is classified under CWE-494: Download of Code Without Integrity Check. Successful exploitation may result in code execution, privilege escalation, information disclosure, and data tampering on affected Linux hosts. The vulnerability requires user interaction and higher attack complexity, but no authentication is needed to trigger the download path. NVIDIA published the advisory in its public product-security repository.

Critical Impact
An attacker who intercepts or substitutes the downloaded installer payload can achieve code execution, escalate privileges, and tamper with data on systems running the NemoClaw Linux installer.

Affected Products

NVIDIA NemoClaw for Linux (installation scripts)
Specific version ranges: Not Available in the published NVD record
Refer to the NVIDIA Security Repository for confirmed fixed versions

Discovery Timeline

2026-08-25 - CVE-2026-65097 published to the National Vulnerability Database (NVD)
2026-08-26 - Last updated in NVD database

Technical Details for CVE-2026-65097

Vulnerability Analysis

The NemoClaw Linux installation scripts fetch code or dependent components from a remote source without verifying the integrity of the retrieved artifacts. Because the installer does not validate digital signatures, cryptographic hashes, or certificate pinning against the downloaded content, an attacker in a position to manipulate the transport or substitute the source can deliver arbitrary code. The installer then executes that code, typically with elevated privileges, during the setup process. This class of weakness is tracked as CWE-494.

Root Cause

The root cause is missing integrity verification of code fetched at install time. Installer scripts that retrieve binaries, tarballs, or auxiliary scripts must validate them against a signed manifest or a known-good hash before execution. The NemoClaw installer omits that check, so any tampered payload delivered through the download channel is treated as trusted input.

Attack Vector

The attack vector is network-based and requires user interaction, such as an administrator running the installer. An attacker who controls an upstream mirror, poisons DNS, performs an on-path (adversary-in-the-middle) attack, or compromises intermediate infrastructure can substitute the payload. Attack complexity is high because the attacker must be positioned to influence the download at execution time.

No verified proof-of-concept code is publicly available. See the NVIDIA advisory and the NVD entry for authoritative technical details.

Detection Methods for CVE-2026-65097

Indicators of Compromise

Unexpected child processes spawned by the NemoClaw installer script during or after installation.
Outbound connections from installer processes to hosts that do not match NVIDIA's documented distribution endpoints.
Files written to system directories with hashes that do not match NVIDIA-published values.
New persistence artifacts (systemd units, cron entries, shell profile edits) created in the installation window.

Detection Strategies

Compare hashes of installer-fetched artifacts against NVIDIA-published reference values before and after deployment.
Enable TLS inspection or egress logging on hosts running the installer to record download URLs and response sizes.
Alert on shell interpreters (bash, sh, python) executed as children of installer scripts running as root.
Track EDR process-lineage telemetry that links installer scripts to unexpected network fetches or binary execution.

Monitoring Recommendations

Audit /tmp, /var/tmp, and installer working directories for transient executables written during setup.
Forward Linux auditd execve and network events for installer host groups into a centralized log platform.
Monitor DNS resolution and TLS SNI for NVIDIA distribution domains to detect redirection or unexpected hosts.

How to Mitigate CVE-2026-65097

Immediate Actions Required

Pause new NemoClaw Linux deployments until a patched installer version identified in the NVIDIA advisory is available and applied.
Restrict installer execution to trusted administrators on isolated management networks with controlled egress.
Verify SHA-256 (or vendor-provided) hashes of any installer-fetched artifacts against NVIDIA's published values prior to execution.

Patch Information

NVIDIA maintains the authoritative fix and version guidance in its public advisory. Consult the NVIDIA product-security repository entry for bulletin 5872 for the fixed installer version, distribution channel, and any post-install remediation steps. Cross-reference the NVD record for CVE-2026-65097 and the CVE.org record for updates.

Workarounds

Download the installer only from NVIDIA's official distribution endpoints over TLS and verify vendor-provided signatures or hashes manually before execution.
Run installers from a hardened bastion or ephemeral build host with egress restricted to NVIDIA endpoints, then transfer verified artifacts to production hosts.
Apply mandatory access controls (SELinux, AppArmor) and least-privilege service accounts to limit the blast radius of installer-driven code execution.

bash

# Configuration example: verify installer-fetched artifacts against a known-good hash
# Replace <expected_sha256> and <artifact> with vendor-published values from the NVIDIA advisory
sha256sum <artifact> | awk '{print $1}' | grep -qx <expected_sha256> \
  && echo "Integrity OK: proceed" \
  || { echo "Integrity FAILED: aborting install"; exit 1; }