NVIDIA Isaac Launchable
CVE-2025-33222
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Isaac Launchable over network
-
DeliverySupply hard-coded credential
-
ExploitAuthenticate as privileged user
-
ExecutionExecute arbitrary code
-
ImpactTamper data or deny service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Credential externalization
MITRE ATT&CK
2 techniques across 2 tactics: Persistence, Credential Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to an NVIDIA Isaac Launchable 1.0 deployment and use of the embedded hard-coded credential (CWE-798) baked into the product; per CVSS PR:N/UI:N no legitimate account or user interaction is needed, so any party who can reach the service and knows or recovers the static credential can authenticate. The primary limiting factor is deployment scope - Isaac Launchable is specialized NVIDIA robotics/simulation tooling with a small footprint - plus the need for network exposure of the affected interface; the input does not specify a non-default configuration requirement, implying default installations are affected. |
| Impact | The input CVSS vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, 9.8 CRITICAL) describes a network-reachable, low-complexity, unauthenticated flaw with full confidentiality, integrity, and availability impact - consistent with CWE-798 hard-coded credentials, where an embedded secret can be recovered and reused by any attacker. However, the exploitation signals temper this: EPSS is only 0.62% (49th percentile), there is no CISA KEV listing, and no public exploit code is referenced, so there is no public exploit identified at time of analysis. The score-vs-likelihood gap is typical of a freshly disclosed, high-severity bug in a low-footprint product that has not yet drawn mass exploitation. No SSVC decision data was provided in the input. Net: a genuinely severe vulnerability by impact and ease of use, but current real-world exploitation pressure appears low given the moderate EPSS, absent KEV/POC, and the niche NVIDIA Isaac Launchable deployment base. Prioritize patching where the product is deployed, but this is not yet an emergency on the level of a KEV-listed, widely-deployed flaw. |
| Exploit ScenarioDerived | An attacker with network access to an NVIDIA Isaac Launchable instance extracts or already knows the hard-coded credential embedded in the product and authenticates without legitimate access. Using that foothold they execute code, escalate privileges, tamper with data, or crash the service. No public proof-of-concept is referenced, and no authentication of their own is required per the CVSS vector (PR:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Unauthenticated remote attackers can bypass authentication in NVIDIA Isaac Launchable 1.0 by using an embedded hard-coded credential (CWE-798), potentially achieving code execution, privilege escalation, denial of service, or data tampering. The issue is rated CVSS 9.8 critical with a PR:N/UI:N vector, meaning no legitimate account or user interaction is required. No CISA KEV listing or public exploit code is identified in the provided data; EPSS is 0.62% (49th percentile).
RemediationAI
No exact fixed version is provided in the available data, so consult NVIDIA's advisory at https://nvidia.custhelp.com/app/answers/detail/a_id/5749 for patch guidance and apply the vendor-released update when confirmed. Until a patched release is available, restrict network access to Isaac Launchable deployments using firewall rules, allowlists, VPNs, or network segmentation so only trusted administrators can reach the affected service; this reduces exposure but may disrupt legitimate remote workflows. Monitor authentication and service logs for use of static or anomalous credentials, rotate any configurable credentials associated with the deployment, and remove or tightly control internet-facing exposure of Isaac Launchable interfaces as a compensating control.
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 vulnerability is CWE-798 (Use of Hard-coded Credentials) in NVIDIA Isaac Launchable, a specialized NVIDIA robotics/simulation tool identified by CPE cpe:2.3:a:nvidia:isaac_launchable:1.0:*:*:*:*:*:*:*. Hard-coded secrets are embedded directly in the product and are not unique per deployment, so an attacker who recovers or knows the static credential can reuse it against any reachable instance. The CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H vector confirms a network-reachable, low-complexity, unauthenticated issue with high confidentiality, integrity, and availability impact. The provided data does not identify the exact protocol or interface carrying the credential, but the advisory and CPE data scope the flaw to Isaac Launchable 1.0 deployments exposed to network access.
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
Hard-coded credential is remotely usable with no attacker auth or interaction (AV:N/AC:L/PR:N/UI:N), yielding full code execution and thus C:H/I:H/A:H.
Primary rating from Vendor (nvidia).
CVSS VectorVendor: nvidia
DescriptionCVE.org
NVIDIA Isaac Launchable contains a vulnerability where an attacker could exploit a hard-coded credential issue. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, denial of service, and data tampering.
Executive ViewAI
NVIDIA Isaac Launchable 1.0 contains an unauthenticated remote authentication bypass via an embedded hard-coded credential that can lead to code execution, privilege escalation, denial of service, or data tampering. Organizations running this version should treat exposed deployments as high risk because no vendor-released patch is identified at time of analysis, and although it is not in CISA KEV and no public exploit identified at time of analysis, the critical severity and lack of patch warrant immediate containment and leadership attention.
No vendor-released patch identified at time of analysis; interim mitigations include isolating NVIDIA Isaac Launchable 1.0 on restricted network segments, blocking internet exposure, enforcing allowlisted access, rotating or removing embedded credentials where possible, monitoring authentication and execution logs, and engaging NVIDIA support for patch guidance.
Threat Intelligence Overview
NVD
CVE.org
EPSS
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
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
NVIDIA Isaac Launchable 1.0 executes launch operations with unnecessary privileges (CWE-250), allowing an attacker who c
Cleartext transmission of sensitive information in NVIDIA Isaac Launchable for Linux (all versions prior to 1.2) exposes
GitHub PoC
Exploit-DB