dbcve.org
Code InjectionWeakness · CWE-94

CVE-2025-33183

HIGH · 7.8 CVSS v3.1 Published 2025-11-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 Isaac-GR00T for all platforms contains a vulnerability in a Python component, where an attacker could cause a code injection issue. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

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 Isaac-GR00T contains a code injection vulnerability in a Python component where untrusted input is improperly handled, allowing an attacker to inject and execute arbitrary code. This could enable complete compromise of the affected system, including code execution, privilege escalation, information disclosure, and data manipulation.

MitigationApply NVIDIA's available security patch when released, implement strict input validation and sanitization on all user-controlled data entering Python components, and restrict network access to the Isaac-GR00T service to minimize attack surface.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Verify NVIDIA Isaac-GR00T installation
    Search for Isaac-GR00T installation directories (commonly under /opt/nvidia/isaac or similar) or check installed packages via pip list, dpkg, or rpm depending on OS. Look for packages named 'isaac-gr00t' or containing 'gr00t' in the name.
    Affected if Isaac-GR00T is found installed on the system
  2. Identify installed Isaac-GR00T version
    Check the version of the installed package using pip show isaac-gr00t, or inspect version files in the installation directory (often named VERSION, __version__.py, or setup.py).
    Affected if Any version of Isaac-GR00T is installed - no specific fixed version is known from this CVE
  3. Locate Python component with code injection vulnerability
    Identify Python scripts or modules within the Isaac-GR00T installation that process external input. Look for endpoints, APIs, or functions that accept user data (command-line arguments, HTTP requests, configuration files) and pass it to eval(), exec(), or similar dangerous functions.
    Affected if A Python component processes untrusted input without sanitization
  4. Check service exposure and accessibility
    Determine if the Isaac-GR00T service is exposed via network ports or APIs. Use netstat, ss, or inspect service configuration files to identify listening ports (common ports may include 5000, 8080, or custom ports). Verify if authentication is required for access.
    Affected if The vulnerable Python component is network-accessible without proper input validation controls
  5. Review system for signs of compromise
    Audit system logs (/var/log/syslog, /var/log/messages, application logs) for suspicious command execution, unexpected Python processes, or anomalous network connections originating from Isaac-GR00T processes. Check for unauthorized SSH keys or cron jobs.
    Affected if Evidence of unauthorized code execution or privilege escalation is found

If NVIDIA Isaac-GR00T is installed and its Python component processes untrusted input (especially if network-accessible), the environment is likely affected by this code injection vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply NVIDIA's available security patch when released, implement strict input validation and sanitization on all user-controlled data entering Python components, and restrict network access to the Isaac-GR00T service to minimize attack surface.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-33183 — 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-2025-33183 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