External risk intelligence

NVIDIA NemoClaw Weak Authentication Leading to Code Execution and Data Tampering.

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-65098

The vulnerability affects a remote-access helper workflow in NVIDIA NemoClaw. Remote-access tools and their associated workflows are commonly deployed as network-accessible services to facilitate connectivity, making them likely to be reachable from the internet or exposed across network boundaries in typical operational environments.

Information Disclosure

Nvidia Nemoclaw

0.0.4 and earlier

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

NVIDIA NemoClaw for Linux has a critical vulnerability in its remote-access component that could allow an unauthorized party to execute code, access sensitive information, or alter data. The issue stems from weak authentication within the helper workflow.

Weak authentication in remote access.
Potential for code execution and data compromise.
Focus on confirming relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could reach the vulnerable component through the network without needing any special access or user interaction. The attack targets a remote-access helper workflow in NVIDIA NemoClaw, potentially allowing an attacker to bypass authentication mechanisms. This could enable them to execute arbitrary code, access sensitive information, or modify data.

Network exposure required.
Weak authentication is the trigger.
Code execution and data compromise risk.

Live Threat

Current exploitation, exposure, and threat context

A vulnerability in NVIDIA NemoClaw's remote-access helper workflow could allow an attacker to bypass weak authentication. This may lead to unauthorized code execution, disclosure of sensitive information, or modification of data, depending on the specific configuration and supported conditions within the advisory.

System data and sensitive information could be exposed.
Weak authentication could be bypassed remotely.
Unauthorized code execution or data tampering may occur.

Operational Fix

Recommended remediation, mitigation, and detection steps

NVIDIA NemoClaw's remote-access helper workflow vulnerability requires immediate attention from teams managing AI/ML platforms and the underlying Linux infrastructure. The first step is to identify all instances of NemoClaw, confirm their network exposure and business criticality, and assign ownership for remediation planning.

Assign to platform or application owners.
Verify NemoClaw's network exposure.
Plan remediation based on risk.

Supplementary metadata

CVSS vector

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Free EASM Trial See How Signal Works

Frequently asked questions

What is NVIDIA NemoClaw?

NVIDIA NemoClaw is a software component designed for Linux environments that facilitates remote-access workflows. It is typically used in AI and machine learning infrastructure to enable remote connectivity and management tasks. Because it functions as a helper service for remote operations, it plays a critical role in maintaining access to computational resources.

What does CWE-1390 mean for CVE-2026-65098?

CWE-1390 refers to a weakness involving the improper checking of authentication mechanisms. In the context of this CVE, it means the software's remote-access workflow fails to properly verify the identity of someone trying to connect. This flaw allows an unauthorized person to bypass security controls, potentially leading to unauthorized code execution, data theft, or tampering.

How is this vulnerability triggered?

The vulnerability is triggered when an attacker reaches the remote-access helper workflow over the network. Because the authentication is weak, the attacker does not need special credentials or prior system access to initiate the exploit. Importantly, this bug requires active network interaction to trigger; it is not triggered by simply running the software in an isolated or offline state.

Why should I be concerned if my NemoClaw is internet-facing?

Halo Surface Signal classifies this vulnerability as external, meaning it is reachable from the internet. Since the remote-access workflow is designed for connectivity, it is often deployed in ways that bridge network boundaries. If your instance is internet-facing, it is directly exposed to remote actors, significantly increasing the risk that they could exploit the weak authentication to compromise your system.

What is the first step to take regarding CVE-2026-65098?

Begin by identifying every server or platform in your environment running NVIDIA NemoClaw versions 0.0.4 or earlier. Once you have a list of affected assets, determine which are accessible over the network. Coordinate with your platform and application teams to verify the business role of these instances and document them to prioritize remediation planning based on their exposure and criticality.

References

Written by Nicholas Merritt

Nicholas Merritt is VP of Security Solutions at Halo Security. With more than 25 years across application security, vulnerability prioritization, and offensive security, he helps teams translate threat data into practical exposure validation and remediation focus. He authors Halo Threat Intelligence CVE advisories using Halo Surface Signal and H/A/L/O context to prioritize internet-facing risk.