dbcve.org
Isaac LaunchableApplication · Nvidia

CVE-2025-33222

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 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.

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 Launchable contains a hard-coded credential vulnerability where authentication credentials are embedded in the software or configuration files. An attacker with knowledge of these credentials could authenticate to the affected system and potentially achieve code execution, privilege escalation, denial of service, or data tampering.

MitigationIdentify and remove all hard-coded credentials from the codebase, rotate any exposed credentials immediately, and implement a proper secrets management solution such as environment variables or a dedicated secrets vault per vendor guidance.

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
Isaac LaunchableApplication
Affected:= 1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm NVIDIA Isaac Launchable version
    Locate the Isaac Launchable installation directory and check the version. On Windows, look in C:\Program Files\NVIDIA Corporation\Isaac Launchable or the installation path used during setup. On Linux, check /opt/nvidia/isaac-launchable or the user-specified path. Look for a version file, manifest, or check the software's about/info panel.
    Affected if The installed version is 1.0
  2. Identify credential-containing files
    Search the Isaac Launchable installation directory for files that commonly store credentials: .env, config.ini, settings.json, credentials.xml, .key, .pem, .cert, secrets.txt, or similar. Use commands like 'find /opt/nvidia/isaac-launchable -type f \( -name "*.env" -o -name "*config*" -o -name "*credential*" -o -name "*.key" \)' on Linux or file explorer search on Windows.
    Affected if Any credential storage files exist within the Isaac Launchable installation directory
  3. Inspect configuration files for embedded secrets
    Open configuration files found in the installation (settings.xml, config.ini, app.config, launch.json, or similar) and examine them for hard-coded values such as passwords, API keys, tokens, shared secrets, or authentication tokens stored as plain text.
    Affected if Plain-text credentials, API keys, tokens, or secrets are found embedded in any configuration files
  4. Search binary and script files for credential patterns
    Use grep or strings utility to scan executables, DLLs, and scripts within the installation for recognizable credential patterns. Search for keywords like 'password=', 'api_key=', 'token=', 'secret=', 'auth=', or base64-encoded strings that may represent credentials.
    Affected if Hard-coded strings resembling credentials (passwords, keys, tokens) are found embedded in executables or scripts
  5. Review application logs for credential exposure
    Check log files in the Isaac Launchable installation (logs directory) for entries that may reveal hard-coded credentials being used during authentication or connection attempts, or error messages exposing credential values.
    Affected if Logs contain exposed credentials or authentication failures revealing static credential values

A system is affected if NVIDIA Isaac Launchable version 1.0 is installed and any hard-coded credentials are discovered within its installation files, configuration, scripts, or binaries.

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

Identify and remove all hard-coded credentials from the codebase, rotate any exposed credentials immediately, and implement a proper secrets management solution such as environment variables or a dedicated secrets vault per vendor guidance.

Fix this in Isaac Launchable 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 help mitigating

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-2025-33222 — 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-33222 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