dbcve.org
NemoclawApplication · Nvidia

CVE-2026-24231

MEDIUM · 6.3 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 0.0.13 or later.
See remediation →
66/100
Remediation priority · Elevated
No privileges

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 validateEndpointUrl() SSRF protection component, where an attacker could cause a server-side request forgery by supplying a crafted endpoint URL referencing the 0.0.0.0/8 address range through a blueprint configuration file or CLI flag. A successful exploit of this vulnerability may 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 · high confidence

NVIDIA NemoClaw contains a flaw in its SSRF protection component validateEndpointUrl() which fails to properly block requests to the 0.0.0.0/8 address range. An attacker with access to supply blueprint configuration files or CLI flags can craft endpoint URLs referencing these addresses to perform server-side request forgery, potentially accessing internal services and disclosing information.

MitigationFix the validateEndpointUrl() function to explicitly block all IPs in the 0.0.0.0/8 range (0.0.0.0 - 0.255.255.255) and ideally other internal/private IP ranges as part of a defense-in-depth SSRF protection strategy.

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.13

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 the command to display the NemoClaw version (e.g., nemoclaw --version, nemoclaw -v, or check the package manifest). Compare the version number to the affected range: versions prior to 0.0.13 are vulnerable.
    Affected if The installed version is lower than 0.0.13
  2. Locate validateEndpointUrl function usage
    Search codebase, logs, or configuration for references to validateEndpointUrl. This function provides SSRF protection and must be present for the vulnerability to be relevant. Inspect any security configuration files or API definitions that reference endpoint validation.
    Affected if validateEndpointUrl is implemented and actively validating endpoint URLs, but the 0.0.0.0/8 range is not blocked (versions < 0.0.13)
  3. Inspect blueprint configuration files
    Review any blueprint, configuration, or schema files that define endpoint URLs or external service connections. Look for files such as blueprints.yaml, config.json, or similar. Search for any URL fields that could reference network endpoints.
    Affected if Blueprint configuration files exist and contain endpoint URL definitions that could be manipulated to point to 0.0.0.0/8 addresses
  4. Check CLI flags and environment variables
    Examine CLI flags, environment variables, or startup parameters that define endpoint URLs or external connections. Review any command-line arguments passed to NemoClaw that include URL parameters.
    Affected if CLI flags or environment variables define endpoint URLs that an attacker could manipulate to reference internal addresses

You are affected if NemoClaw version is lower than 0.0.13 and endpoint URL validation (validateEndpointUrl) is in use with configuration files or CLI flags that define endpoint URLs.

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.13 or later
Fixed in 0.0.13
Interim mitigation

Fix the validateEndpointUrl() function to explicitly block all IPs in the 0.0.0.0/8 range (0.0.0.0 - 0.255.255.255) and ideally other internal/private IP ranges as part of a defense-in-depth SSRF protection strategy.

Recommended fix Moderate confidence

0.0.13

  1. 1. Identify the current installed version of Nemoclaw by running: pip show nemoclaw or pip list | grep -i nemoclaw
  2. 2. Upgrade Nemoclaw to version 0.0.13 or later using pip: pip install --upgrade nemoclaw>=0.0.13
  3. 3. Verify the upgrade was successful by checking the installed version: pip show nemoclaw
  4. 4. If using a requirements.txt or environment file, update the version constraint to require nemoclaw>=0.0.13
  5. 5. Rebuild or redeploy any services or containers that use Nemoclaw to ensure they run the patched version
  6. 6. Test that the validateEndpointUrl() function properly rejects 0.0.0.0/8 address range URLs as expected

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-24231 — 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-24231 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