dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2025-23356

HIGH · 8.4 CVSS v3.1 Published 2025-10-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
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 Lab contains a vulnerability in SB3 configuration parsing. A successful exploit of this vulnerability might lead to code execution, denial of service, escalation of privileges, information disclosure, or 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 · low confidence

NVIDIA Isaac Lab contains a vulnerability in SB3 (Stable Baselines3) configuration parsing that could allow attackers to achieve code execution, denial of service, privilege escalation, information disclosure, or data tampering through malicious configuration input.

MitigationUntil an official patch is released, restrict access to Isaac Lab environments, validate all SB3 configuration inputs, and avoid loading untrusted configuration files. Monitor NVIDIA's security bulletins for updates.

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

CVSS:3.1/AV:L/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. Verify NVIDIA Isaac Lab installation
    Check for Isaac Lab installation by looking for the isaaclab directory in your environment (e.g., check ~/.local/share/isaaclab, /opt/isaaclab, or the directory where you cloned the Isaac Lab repository). Also verify the Python package is installed: pip show isaaclab or python -c 'import isaaclab; print(isaaclab.__file__)'
    Affected if NVIDIA Isaac Lab is installed on the system
  2. Determine installed Isaac Lab version
    Run 'python -c "import isaaclab; print(isaaclab.__version__)"' or check the version.py/VERSION file in the Isaac Lab installation directory. Compare against any released versions since early 2025.
    Affected if The installed version is any release of NVIDIA Isaac Lab that includes SB3 integration
  3. Identify SB3 configuration files in use
    Search for SB3-related configuration files in your Isaac Lab projects: look for files containing 'stable_baselines3', 'sb3', or 'rl_config' in names. Check directories like configs/, experiments/, or custom run directories. Also examine any .yaml, .json, or .py config files that define RL training parameters.
    Affected if SB3 configuration files exist and are being loaded by Isaac Lab for reinforcement learning workflows
  4. Inspect configuration file validation
    Examine the code that loads SB3 configs: look for files in isaaclab/scripts or isaaclab/robots that handle configuration loading. Check if there is explicit input validation (schema validation, type checking, allowlist filtering) before configs are parsed. Search for functions that load yaml/json configs for SB3 and verify if they perform sanitization.
    Affected if Configuration files are loaded without proper validation checks on their contents
  5. Check for custom or user-supplied configs
    Review any custom SB3 configuration files you have created or downloaded. Examine the contents for unusual Python code patterns (eval, exec, __import__), shell commands, or suspicious parameter values that could indicate attempted injection. Check if user-provided config paths are directly passed to loading functions.
    Affected if Custom or untrusted SB3 configuration files are used without prior review

You are affected if NVIDIA Isaac Lab with SB3 integration is installed and SB3 configuration files are loaded without validation of their contents.

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

Until an official patch is released, restrict access to Isaac Lab environments, validate all SB3 configuration inputs, and avoid loading untrusted configuration files. Monitor NVIDIA's security bulletins for updates.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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