NVIDIA NemoClaw: weak authentication in the remote-access helper workflow

Impact

A remote-access helper is by definition a path onto the machine, and NVIDIA states its authentication is weak. The listed outcomes are code execution, information disclosure and data tampering, so a caller who defeats that authentication acts on the node rather than merely reading from it. On a GPU node this is the kind of access that reaches whatever the workload holds - datasets, checkpoints, tokens - and a node you suspect was reached this way cannot be cleared without draining it. The record does not describe how weak the authentication is, so scope the exposure by who can reach the helper's listener.

Who can reach it

Network-reachable attacker who can talk to the remote-access helper (CVSS AV:N/PR:N/AC:H). No valid credentials are stated as required.

What to do

Apply the fixed version listed in NVIDIA product-security bulletin 5872; the CVE record names none. Meanwhile restrict the helper's listener to a management network or disable the remote-access workflow where it is not needed, and restart the service after updating.

References

Related entries

• NVIDIA NemoClaw: inference service comes up without authentication, reachable from the adjacent networkCVE-2026-65105 · NVIDIA NemoClaw for Linux (inference server setup)High
• ClearML client SDK: Deserialization of untrusted dataCVE-2024-24590 · ClearML client SDKHigh
• ClearML client SDK: Path traversal — a malicious dataset writes arbitrary files on the consumerCVE-2024-24591 · ClearML client SDKHigh
• Keras (`utils.get_file`): Path traversal in tar extraction in 3.11.3 (incomplete fix)CVE-2025-12638 · Keras (`utils.get_file`)High
• vLLM (multi-node ZeroMQ): Secondary vLLM host trusts unauthenticated ZeroMQ messagesCVE-2025-30165 · vLLM (multi-node ZeroMQ)High
• Kubeflow Community Distribution: Insecure default in the platform installCVE-2026-47237 · Kubeflow Community DistributionHigh