dbcve.org
NemoclawApplication · Nvidia

CVE-2026-24222

HIGH · 8.6 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 0.0.18 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
NVIDIA NeMoClaw contains a vulnerability in the sandbox environment initialization component, where a remote attacker could 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 might lead to information disclosure.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

NVIDIA NeMoClaw contains an improper access control vulnerability in its sandbox environment initialization. A remote attacker can exploit prompt injection to cause the AI agent to read and exfiltrate host environment variables that are not properly restricted during sandbox creation. The sandbox fails to isolate or deny access to sensitive environment variables, leading to information disclosure.

MitigationRestrict sandbox environment variable access during initialization by implementing strict isolation policies, removing or masking sensitive variables before agent execution, and adding input validation to detect and block prompt injection attempts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NemoclawApplication
Affected:< 0.0.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed NeMoClaw version
    Run 'pip show nemoclaw' or check the package version in your Python environment
    Affected if The installed version is lower than 0.0.18
  2. Confirm sandbox environment is in use
    Check if your NeMoClaw deployment uses the sandbox feature for AI agent execution - review your configuration files or runtime settings
    Affected if Sandbox environment is enabled and the version is below 0.0.18
  3. Inspect environment variable exposure in sandbox
    Execute a test prompt within the NeMoClaw sandbox that attempts to access environment variables (e.g., request $PATH, $HOME, or other system variables) and observe if they are returned
    Affected if The sandbox returns host environment variable values instead of blocking or masking them
  4. Verify sensitive variable isolation
    Within the sandbox, attempt to access potentially sensitive variables such as AWS_SECRET_ACCESS_KEY, API keys, or database credentials if present in the host environment
    Affected if Sensitive environment variables from the host are readable from within the sandbox

You are affected if NeMoClaw version is below 0.0.18 and the sandbox environment exposes host environment variables to the AI agent.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.0.18 or later
Fixed in 0.0.18
Interim mitigation

Restrict sandbox environment variable access during initialization by implementing strict isolation policies, removing or masking sensitive variables before agent execution, and adding input validation to detect and block prompt injection attempts.

Recommended fix High confidence

NeMoClaw version 0.0.18

  1. Upgrade NeMoClaw to version 0.0.18 or later to receive the sandbox environment initialization fix
  2. Verify the upgrade by checking the installed version using the package manager or version command
  3. Test that the sandbox environment properly restricts access to host environment variables after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nemoclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24222 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24222 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data