Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-23304: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in NVIDIA NVIDIA NeMo Framework

0
High
VulnerabilityCVE-2025-23304cvecve-2025-23304cwe-22
Published: Wed Aug 13 2025 (08/13/2025, 17:16:12 UTC)
Source: CVE Database V5
Vendor/Project: NVIDIA
Product: NVIDIA NeMo Framework

Description

NVIDIA NeMo library for all platforms contains a vulnerability in the model loading component, where an attacker could cause code injection by loading .nemo files with maliciously crafted metadata. A successful exploit of this vulnerability may lead to remote code execution and data tampering.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/27/2026, 01:01:55 UTC

Technical Analysis

CVE-2025-23304 is a path traversal vulnerability classified under CWE-22 found in the NVIDIA NeMo Framework, a toolkit widely used for building and deploying AI models. The vulnerability resides in the model loading component that processes .nemo files, which contain model metadata. Due to improper limitation of pathname access, an attacker can craft malicious .nemo files with specially designed metadata that bypasses directory restrictions, enabling them to inject arbitrary code during the model loading process. This can lead to remote code execution (RCE), allowing attackers to execute arbitrary commands with the privileges of the process running NeMo. Additionally, data tampering is possible, compromising the integrity of AI models and potentially altering their behavior. The vulnerability affects all versions prior to 2.3.2 and requires low privileges and local access but does not require user interaction. The CVSS v3.1 score of 7.8 reflects high severity, with high impact on confidentiality, integrity, and availability. While no exploits are currently known in the wild, the nature of the flaw makes it a significant risk for organizations leveraging NVIDIA NeMo in AI workflows. The vulnerability was reserved in January 2025 and published in August 2025, indicating a recent discovery and disclosure. No official patch links are provided yet, but upgrading to version 2.3.2 or later is advised once available. The flaw highlights the importance of secure file handling and validation in AI frameworks to prevent supply chain and code injection attacks.

Potential Impact

The vulnerability poses a critical risk to organizations using NVIDIA NeMo Framework for AI model development and deployment. Exploitation can lead to remote code execution, allowing attackers to gain control over affected systems, potentially leading to unauthorized access, data theft, or disruption of AI services. Data tampering risks undermine the integrity and trustworthiness of AI models, which can have cascading effects in applications relying on these models for decision-making, such as autonomous systems, healthcare, finance, and more. The requirement for low privileges and no user interaction lowers the barrier for exploitation, increasing the threat surface. Organizations with AI infrastructure that integrates NVIDIA NeMo are at risk of targeted attacks aiming to compromise AI pipelines or leverage compromised systems for lateral movement. The vulnerability also threatens availability if attackers disrupt AI services or corrupt models. Given the growing adoption of AI frameworks globally, the impact can be widespread, affecting both private sector and critical infrastructure entities.

Mitigation Recommendations

1. Immediately upgrade NVIDIA NeMo Framework to version 2.3.2 or later once patches are available to address this vulnerability. 2. Implement strict validation and sanitization of all .nemo files before loading, ensuring metadata does not contain path traversal sequences or unauthorized file references. 3. Restrict file system permissions for directories used by NeMo to prevent unauthorized file creation or modification. 4. Employ application whitelisting and runtime application self-protection (RASP) to detect and block anomalous code execution attempts within AI model loading processes. 5. Monitor logs and file access patterns for suspicious activity related to .nemo file handling. 6. Isolate AI model loading environments using containerization or sandboxing to limit the impact of potential exploitation. 7. Educate developers and system administrators about secure handling of AI model files and the risks of loading untrusted models. 8. Coordinate with NVIDIA support and subscribe to security advisories for timely updates and patches.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
nvidia
Date Reserved
2025-01-14T01:06:27.218Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 689ccc41ad5a09ad004f80ea

Added to database: 8/13/2025, 5:32:49 PM

Last enriched: 2/27/2026, 1:01:55 AM

Last updated: 3/24/2026, 11:08:30 AM

Views: 142

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses