Skip to main content

NVIDIA Isaac Launchable CVE-2025-33224

CRITICAL
Execution with Unnecessary Privileges (CWE-250)
2025-12-23 psirt@nvidia.com
9.8
CVSS 3.1 · Vendor: nvidia
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain input access to Isaac Launchable
  2. Delivery
    Supply crafted/malicious input
  3. Exploit
    Trigger over-privileged execution path
  4. Execution
    Execute code in elevated context
  5. Impact
    Escalate to full host compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V8 - Authorization Unnecessary privilege execution
Exploitation Conditions

The CVE description (CWE-250, Execution with Unnecessary Privileges) indicates the required condition is interaction with an NVIDIA Isaac Launchable (version 1.0) component that runs with more privileges than necessary; the concrete trigger - the specific interface, input, or launchable configuration - is not named in the provided description and must be obtained from NVIDIA advisory a_id/5749. Limiting factors: exploitation is bounded to environments that actually deploy Isaac Launchable (a specialized NVIDIA robotics/AI developer product), which sharply narrows the exposed population; while the supplied CVSS vector lists PR:N/UI:N, the privilege-scoping nature of CWE-250 suggests a precondition such as an existing foothold or the ability to feed input to the privileged component, so real-world exploitation likely depends on prior access rather than pure anonymous remote reach.

Impact

The input assigns a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), which on its face describes a remote, unauthenticated, low-complexity flaw with total confidentiality, integrity, and availability impact - a worst-case profile. However, this rating is in tension with the underlying weakness, CWE-250 (Execution with Unnecessary Privileges), which typically describes a component running with more rights than needed so that a separate foothold is escalated, rather than a directly network-reachable entry point. The terse NVIDIA description ('an attacker could cause an execution with unnecessary privileges') does not specify a remote network vector or the delivery mechanism, so the AV:N/PR:N/UI:N metric choices cannot be independently corroborated from the description and should be verified against NVIDIA advisory a_id/5749. On the real-world signals: this is not in CISA KEV and no public exploit code is referenced, so exploitation status is 'no public exploit identified at time of analysis.' EPSS is 0.81% (56th percentile) - low-to-moderate and unremarkable, which is consistent with the absence of known exploitation and argues against treating this as an active, widespread threat despite the high CVSS. No SSVC decision data was provided. Net: the 9.8 overstates likely real-world urgency for most defenders; priority should be driven by whether an organization actually deploys NVIDIA Isaac Launchable, with patching scheduled on normal cadence rather than emergency timelines.

Exploit ScenarioDerived

An attacker with the ability to interact with or supply input to an NVIDIA Isaac Launchable component leverages the fact that the component runs with unnecessarily elevated privileges to execute code or actions in that privileged context. Given the CWE-250 nature, this most plausibly chains from an existing low-privilege foothold or a crafted input into the launchable, yielding escalation and full compromise of the host. No public proof-of-concept is referenced in the provided data.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 19, 2026

NVIDIA Isaac Launchable 1.0 runs components with more privileges than their function requires (CWE-250), so an attacker who can reach or drive those privileged execution paths could obtain code execution, escalate privileges, cause denial of service, or tamper with and disclose data. Only environments that actually deploy Isaac Launchable - a specialized NVIDIA robotics/AI developer component - are exposed, which sharply limits the affected population, and no public exploit code or CISA KEV entry was identified at time of analysis; EPSS is 0.81% (56th percentile), consistent with low observed exploitation activity. Note a scoring divergence: NVIDIA/NVD publishes 9.8 with AV:N/AC:L/PR:N/UI:N, while our assessment scopes the realistic attack vector to local access with low privileges (AV:L/AC:L/PR:L/UI:N), since the privilege-scoping weakness most plausibly requires an existing foothold or the ability to feed input to the over-privileged launchable rather than anonymous remote reach.

RemediationAI

Patch status is not specified in the provided data, so no fixed version number can be cited here; consult NVIDIA advisory a_id/5749 (https://nvidia.custhelp.com/app/answers/detail/a_id/5749) for the exact remediated release and upgrade Isaac Launchable 1.0 to it as the primary fix, validating afterwards that the launchable no longer runs with elevated rights. Until that upgrade is applied, apply least-privilege containment: run Isaac Launchable as a dedicated non-root account with no sudo rights and drop unneeded Linux capabilities or device mounts from its container/launch configuration (trade-off: some GPU or hardware-access features may require selective capability grants that must be re-tuned per workflow); restrict the host to an isolated developer/CI network segment and block inbound access to any service or port the launchable exposes (trade-off: remote team access to the tooling must be brokered through a bastion or VPN); and avoid running the launchable on shared multi-tenant build hosts where an untrusted user could already hold the low-privilege foothold our assessment assumes (trade-off: reduced host consolidation and higher infrastructure cost). Log and monitor process launches that inherit elevated privileges from the launchable, and review file and device permissions granted to it as an early indicator of abuse, since no public exploit code was identified at time of analysis but the underlying privilege misconfiguration remains exploitable once a foothold exists.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-250, Execution with Unnecessary Privileges: the launchable and the processes it spawns are granted broader permissions (filesystem, device, or service rights) than their intended operation demands, so any input path or interface that reaches them inherits that excess authority. Because the flaw is one of privilege scoping rather than memory corruption, the practical exploitation surface is whatever interface, configuration, or input the launchable accepts - the specific trigger is not named in the CVE description and must be read from NVIDIA advisory a_id/5749. CPE data confirms the affected package is nvidia:isaac_launchable:1.0, i.e., a single versioned release of the launchable tooling that sits alongside NVIDIA's Isaac robotics developer stack; no other versions are enumerated. The privilege boundary being crossed determines the true blast radius: on a developer workstation or shared build host, an attacker with the low-privilege foothold assumed by our assessed vector (AV:L/PR:L) can potentially pivot to the launchable's higher-privileged context to execute code, read or alter project data, or crash services. The published CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C/I/A High) should be treated as a vendor worst-case ceiling that is not corroborated by the privilege-escalation nature of the weakness or by the narrow deployment footprint.

Know when Isaac Launchable gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (nvidia) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

CWE-250 over-privileged execution typically requires a local foothold or input-supply capability, so AV:L and PR:L are more defensible than the input's AV:N/PR:N; impacts remain high across C/I/A.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (nvidia).

CVSS VectorVendor: nvidia

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

NVIDIA Isaac Launchable contains a vulnerability where an attacker could cause an execution with unnecessary privileges. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, information disclosure and data tampering.

Executive ViewAI

Why It Matters

NVIDIA Isaac Launchable 1.0 carries a critical privilege-scoping weakness that could enable code execution, privilege escalation, denial of service, or data tampering in environments running this specialized robotics/AI development component. Business exposure is confined to teams that actually deploy Isaac Launchable, and no public exploit identified at time of analysis; EPSS is 0.8%, consistent with low observed exploitation activity. Leadership should prioritize confirming deployment and reducing local access to over-privileged launchable paths because no vendor-released patch identified at time of analysis.

Business Impact: Medium
Compensating Controls

No vendor-released patch identified at time of analysis; restrict local access to Isaac Launchable 1.0 execution paths to trusted users, enforce least privilege, isolate affected development hosts, monitor for privilege escalation or data tampering, and track the NVIDIA advisory for a fixed release.

Threat Intelligence Overview

EPSS Score
0.8%
Top 44% exploitable
Prevalence
Low
niche NVIDIA robotics/AI developer tooling, not broad enterprise footprint
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.8%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact
Medium

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Affected Products (CPE)CVE.org

cpe:2.3:a:nvidia:isaac_launchable:1.0:*:*:*:*:*:*:*

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy