To address the vulnerability identified in CVE-2026-24222 (and the related SSRF risk in CVE-2026-24231) – 5th May -2026

Preface: While NVIDIA has not “dropped” support for the core OpenClaw framework, in some specific cases they have moved away from its standard form.

Background: Because NemoClaw “bakes” certain variables into the sandbox configuration during onboarding, if they are not correctly scoped or sanitized, they remain accessible to the agent process even though it should be isolated.

As a result, this allows an attacker to exfiltrate critical secrets (like the NVIDIA_API_KEY or TELEGRAM_BOT_TOKEN mentioned) through the agent’s existing communication channels.

To address the vulnerability identified in CVE-2026-24222 (and the related SSRF risk in CVE-2026-24231), admin should use the following CLI flags during sandbox creation or update. These flags, introduced in NemoClaw v0.0.18, are designed to strictly control which host environment variables are “baked” into the sandbox environment.

For details, see attached diagram.

Vulnerability details:

CVE-2026-2422 NVIDIA NemoClaw contains a vulnerability in the sandbox environment initialization component where a remote attacker may cause improper access control by sending prompt-injected content that causes the agent to read and exfiltrate host environment variables not properly restricted during sandbox creation. A successful exploit of this vulnerability may lead to information disclosure.

CVE-2026-24231 NVIDIA NemoClaw contains a vulnerability in the validateEndpointUrl() SSRF protection component where an attacker may cause a server-side request forgery by supplying a crafted endpoint URL referencing the 0[.]0[.]0[.]0/8 address range via a blueprint configuration file or CLI flag. A successful exploit of this vulnerability may lead to information disclosure.

Official announcement: Please refer to the link for details – https://nvidia.custhelp.com/app/answers/detail/a_id/5837

Recommended Action:
NVIDIA has released a software update for NVIDIA NemoClaw to address this issue. Users should update to version v0.0.18 or later immediately, as the privilege escalation fixes are critical.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.