NVIDIA Isaac Launchable
CVE-2025-33223
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Isaac Launchable interface
-
DeliveryInvoke affected launch component
-
ExploitAbuse unnecessary privileges
-
ExecutionExecute code in elevated context
-
ImpactEscalate privileges / tamper data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V8 - Authorization Unnecessary privilege execution
|
| Exploitation Conditions | The input does not name a specific feature, protocol or configuration toggle - NVIDIA's description only states that Isaac Launchable performs 'an execution with unnecessary privileges' (CWE-250), meaning the launch component runs in a more privileged context than required. The vendor CVSS vector claims no special conditions (PR:N/UI:N/AC:L), implying unauthenticated remote reachability against affected Isaac Launchable 1.0, but CWE-250 typically requires that an attacker first be able to influence what the over-privileged process executes (e.g. reaching the launch mechanism or supplying input it runs), which usually presupposes network/service exposure or an existing foothold. Limiting factors: affected scope is restricted to Isaac Launchable version 1.0 (a niche robotics tool), exploitation realistically depends on the over-privileged launch path being exposed, and the exact prerequisite must be confirmed from NVIDIA advisory 5749 before assuming default-configuration remote exploitation. |
| Impact | The vendor-supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N, C:H/I:H/A:H = 9.8 Critical) describes a remotely exploitable, unauthenticated flaw with full impact to confidentiality, integrity and availability. However, the underlying weakness is CWE-250 (Execution with Unnecessary Privileges), which almost always manifests as a privilege/context problem reached through an existing foothold rather than a direct remote network entry point - so the AV:N/PR:N labeling is in tension with the CWE and with the deliberately vague NVIDIA description ('could cause an execution with unnecessary privileges'). This should be verified with NVIDIA advisory 5749, because CWE-250 flaws are frequently local/config-dependent despite high CVSS scores. Supporting exploitation signals are modest and do not corroborate the Critical rating: EPSS is only 0.69% (52nd percentile), there is no CISA KEV listing, and no public exploit was identified in the provided data. The combination (very high CVSS but low EPSS, no KEV, no POC, and a CWE that implies constrained preconditions) suggests this is a theoretically severe but not yet actively exploited issue - patch on a normal-to-prompt cycle rather than emergency, and confirm the true attack vector with the vendor before treating it as internet-facing unauthenticated RCE. |
| Exploit ScenarioDerived | An attacker who can reach an affected NVIDIA Isaac Launchable deployment leverages the component's execution with unnecessary privileges to run code in a higher-privileged context, resulting in code execution, privilege escalation, data tampering, information disclosure or denial of service. No public exploit code was identified at time of analysis, and the precise entry point is under-specified by the vendor; the CVSS claim of low-complexity unauthenticated network access (AV:N/AC:L/PR:N) should be validated against NVIDIA advisory 5749 since CWE-250 often requires a prior local foothold. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
NVIDIA Isaac Launchable 1.0 executes launch operations with unnecessary privileges (CWE-250), allowing an attacker who can influence the launch path to inherit the component's elevated rights and potentially achieve code execution, privilege escalation, denial of service, information disclosure, or data tampering. NVIDIA's advisory assigns CVSS 9.8 (AV:N/AC:L/PR:N/UI:N), but independent analysis assesses local, low-privileged exploitation (AV:L/AC:L/PR:L/UI:N) as the more realistic precondition pending confirmation of exposure requirements from NVIDIA advisory 5749. No public exploit code or CISA KEV entry was identified at time of analysis; EPSS is 0.69%.
RemediationAI
No exact fixed version is identified in the provided data; consult NVIDIA advisory 5749 (https://nvidia.custhelp.com/app/answers/detail/a_id/5749) for the vendor-released patch or upgrade path and apply it to Isaac Launchable 1.0 installations. Until a fixed release is confirmed, reduce exposure by restricting who can invoke or influence the Isaac Launchable launch path, running the component under a dedicated least-privilege account with unnecessary capabilities dropped, and isolating it in a container or host with no broader privileges than the robotics workload requires. If the launch interface is network-reachable, limit it to trusted management networks or localhost via firewall rules or bind-address changes; the trade-off is reduced remote manageability. Avoid running Isaac Launchable as root or with elevated service credentials, since that preserves the CWE-250 condition; the trade-off is possible breakage of workflows that assume elevated access. Monitor for unexpected child processes or privilege changes spawned by the launch component.
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 flaw is CWE-250 (Execution with Unnecessary Privileges), meaning the Isaac Launchable component performs launch operations in a security context more privileged than the task requires. The supplied CPE limits affected scope to nvidia:isaac_launchable:1.0. No specific exposed service, protocol, or configuration toggle is named in the provided data, so exploitation requires confirming how an attacker can influence the over-privileged launch path, typically by reaching the launch mechanism or supplying input that it executes. NVIDIA's CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8) claims remote unauthenticated reachability, but the independent assessment (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) treats local low-privileged exploitation as the more defensible precondition until NVIDIA advisory 5749 clarifies exposure. Successful abuse could yield code execution in the elevated context, privilege escalation, denial of service, information disclosure, and data tampering.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CWE-250 execution with unnecessary privileges typically needs a local foothold/limited access to drive the over-privileged process, so AV:L and PR:L; full C/I/A impact retained per vendor.
Primary rating from Vendor (nvidia).
CVSS VectorVendor: nvidia
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
NVIDIA Isaac Launchable 1.0 carries a critical privilege-handling flaw that could allow an attacker who can influence launch operations to inherit elevated rights, with possible code execution, privilege escalation, denial of service, information disclosure, or data tampering. Organizations using this release in development or production workflows should treat it as a high-priority exposure because no vendor-released patch identified at time of analysis, although no public exploit identified at time of analysis. Leadership should prioritize inventory, access restriction, and isolation of affected NVIDIA Isaac environments to reduce operational and data-integrity risk.
No vendor-released patch identified at time of analysis. Restrict access to NVIDIA Isaac Launchable 1.0 launch paths to least-privileged trusted users, isolate affected environments, enforce launch-path permissions and application allowlisting, monitor for anomalous launch operations, and engage NVIDIA via advisory 5749 for patch and exposure guidance.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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
More in Isaac Launchable
View allNVIDIA Isaac Launchable 1.0 runs components with more privileges than their function requires (CWE-250), so an attacker
Unauthenticated remote attackers can bypass authentication in NVIDIA Isaac Launchable 1.0 by using an embedded hard-code
Cleartext transmission of sensitive information in NVIDIA Isaac Launchable for Linux (all versions prior to 1.2) exposes
NVD
CVE.org
EPSS
GitHub PoC
Exploit-DB