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-33250: CWE-94 Improper Control of Generation of Code ('Code Injection') in NVIDIA NeMo Framework

0
High
VulnerabilityCVE-2025-33250cvecve-2025-33250cwe-94
Published: Wed Feb 18 2026 (02/18/2026, 13:56:28 UTC)
Source: CVE Database V5
Vendor/Project: NVIDIA
Product: NeMo Framework

Description

NVIDIA NeMo Framework contains a vulnerability where an attacker could cause remote code execution. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

AI-Powered Analysis

AILast updated: 02/18/2026, 14:27:53 UTC

Technical Analysis

CVE-2025-33250 is a vulnerability classified under CWE-94, indicating improper control over code generation, specifically code injection, within the NVIDIA NeMo Framework. NeMo is a toolkit designed for building and training conversational AI models, widely used in AI research and development environments. The vulnerability affects all versions prior to 2.6.1 and allows an attacker with local access and limited privileges to execute arbitrary code remotely without requiring user interaction. The CVSS 3.1 score of 7.8 reflects a high severity, with attack vector local (AV:L), low attack complexity (AC:L), requiring low privileges (PR:L), and no user interaction (UI:N). The scope is unchanged (S:U), but confidentiality, integrity, and availability impacts are all high (C:H/I:H/A:H). This means a successful exploit could lead to full system compromise, including running malicious code, disrupting services, tampering with data, and leaking sensitive information. Although no exploits are known in the wild yet, the vulnerability's characteristics make it a critical concern for environments running NeMo, especially where multiple users or untrusted code execution is possible. The lack of a patch link in the provided data suggests that remediation involves upgrading to version 2.6.1 or later, where the issue is presumably fixed. The vulnerability was reserved in April 2025 and published in February 2026, indicating a recent disclosure. Organizations leveraging NeMo for AI workloads must prioritize patching and review access controls to mitigate exploitation risks.

Potential Impact

For European organizations, the impact of CVE-2025-33250 is significant, particularly for those involved in AI research, development, and deployment using NVIDIA's NeMo Framework. Successful exploitation could lead to unauthorized code execution, enabling attackers to manipulate AI models, corrupt data, or disrupt AI-driven services. This could affect sectors such as automotive, healthcare, finance, and telecommunications, where AI models are increasingly integrated. Confidentiality breaches could expose sensitive training data or proprietary algorithms, while integrity violations might result in corrupted AI outputs or decision-making processes. Availability impacts could disrupt critical AI services or research activities. Given the local attack vector but low complexity and no user interaction required, insider threats or compromised internal systems pose a notable risk. The absence of known exploits currently provides a window for proactive defense, but the high severity demands urgent attention to prevent potential future attacks.

Mitigation Recommendations

1. Upgrade the NVIDIA NeMo Framework to version 2.6.1 or later immediately to apply the official fix for CVE-2025-33250. 2. Restrict local access to systems running NeMo to trusted users only, employing strict access controls and monitoring for unusual activity. 3. Implement application whitelisting and sandboxing to limit the ability of unauthorized code execution within AI development environments. 4. Conduct regular audits of user privileges and remove unnecessary local privileges that could facilitate exploitation. 5. Monitor logs and system behavior for signs of code injection or anomalous processes related to NeMo usage. 6. Educate AI development teams about the risks of code injection vulnerabilities and enforce secure coding and deployment practices. 7. If upgrading immediately is not feasible, consider isolating NeMo workloads in segmented network zones to reduce attack surface. 8. Stay updated with NVIDIA security advisories for any patches or mitigations related to this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
nvidia
Date Reserved
2025-04-15T18:51:08.847Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6995c8846aea4a407a9d0ccd

Added to database: 2/18/2026, 2:11:16 PM

Last enriched: 2/18/2026, 2:27:53 PM

Last updated: 2/21/2026, 12:20:15 AM

Views: 5

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 in Console -> Billing for AI refresh and higher limits.

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

Latest Threats