Skip to main content

Bionemo Framework EUVDEUVD-2026-17518

| CVE-2026-24165 HIGH
Deserialization of Untrusted Data (CWE-502)
2026-03-31 nvidia
8.8
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    User opens malicious serialized file
  2. Exploit
    BioNeMo deserializes untrusted data
  3. Execution
    Attacker code executes with user privileges
  4. Impact
    System compromise achieved

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V1 - Encoding and Sanitization Safe deserialization, type allowlists
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Local attacker with physical or logical access to NVIDIA BioNeMo system. Victim must open/interact with a crafted file or data object triggering unsafe deserialization. Default installations are vulnerable; no special configuration required.

Impact

Real-world risk is moderate despite the High CVSS score. The CVSS vector (AV:L/AC:L/PR:N/UI:R) indicates local attack vector with low complexity but requires user interaction-an attacker must convince a researcher to open a malicious model file, dataset, or configuration. This significantly limits exploitability compared to remotely exploitable vulnerabilities. The PR:N (no privileges required) designation means an unauthenticated local user could trigger the flaw, but the UI:R (user interaction required) acts as a natural brake on automated exploitation. EPSS probability data is unavailable for this recent CVE, and no public exploit identified at time of analysis. However, deserialization exploits are well-understood, and proof-of-concept development would be straightforward for attackers familiar with Python serialization libraries. The SSVC framework would likely categorize this as requiring user interaction (not automatable), with technical impact of total system compromise given the RCE potential. Priority should be medium-high for organizations using BioNeMo in multi-user research environments where untrusted model files might be processed.

Exploit ScenarioDerived

An attacker creates a malicious BioNeMo model file or configuration containing a serialized Python object with embedded code execution payload. The attacker distributes this file through academic collaboration channels, model-sharing repositories, or compromised research datasets. When a legitimate researcher downloads and loads the malicious file into their BioNeMo environment, the framework deserializes the untrusted data, triggering arbitrary code execution with the privileges of the BioNeMo process. The attacker gains control of the research workstation or cloud instance, potentially exfiltrating proprietary drug discovery data, computational research results, or pivoting to connected high-performance computing infrastructure.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 31, 2026

Deserialization of untrusted data in NVIDIA BioNeMo Framework enables local attackers to execute arbitrary code, cause denial of service, disclose sensitive information, or tamper with data when users open malicious files. CVSS 7.8 (High) reflects local attack vector requiring user interaction. EPSS data not available; no public exploit identified at time of analysis. Affects NVIDIA BioNeMo Framework, a platform for AI-driven drug discovery and biomolecular research.

RemediationAI

Organizations should immediately consult NVIDIA's official security bulletin at https://nvidia.custhelp.com/app/answers/detail/a_id/5808 for patched versions and upgrade guidance. Patch available per vendor advisory, though specific remediated version numbers are not confirmed in available data at time of analysis. As an interim mitigation, restrict BioNeMo framework access to trusted users only, implement strict input validation for all model files and configuration data before deserialization, and employ sandboxing or containerization to limit blast radius of potential exploitation. Consider disabling or restricting deserialization features for external data sources until patching is complete. Organizations should also audit existing model repositories for potentially malicious serialized objects and establish policies requiring cryptographic signing of trusted model files.

Affected VersionsENISA

BioNeMo Framework All versions that do not include commit e5e58c8

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability stems from CWE-502 (Deserialization of Untrusted Data), a class of flaws where applications deserialize externally-controlled data without proper validation. The NVIDIA BioNeMo Framework (CPE: cpe:2.3:a:nvidia:bionemo_framework) likely accepts serialized objects from user-provided files or inputs during machine learning model loading, configuration parsing, or data processing workflows. When Python pickle, YAML, or similar serialization formats are used without sanitization, attackers can embed malicious payloads that execute during deserialization. In scientific computing frameworks like BioNeMo, which process complex biomolecular datasets and pretrained models, deserialization vulnerabilities are particularly concerning as researchers routinely share model files and configuration data across institutions.

Know when Bionemo Framework gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.8 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
CVSS changed
Jul 24, 2026 - 20:22 NVD
7.8 (HIGH) 8.8 (HIGH)
CVE Published
Mar 31, 2026 - 16:24 nvd
HIGH 7.8

DescriptionNVD

NVIDIA BioNeMo contains a vulnerability where a user could cause a deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

Executive ViewAI

Why It Matters

NVIDIA BioNeMo Framework contains a deserialization vulnerability (CVE-2026-24165) that allows local attackers to execute arbitrary code or cause denial of service when users open malicious files, impacting organizations using this AI platform for drug discovery and biomolecular research. Without vendor patching currently available, organizations must immediately inventory usage and restrict file handling until remediation is released.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict BioNeMo Framework access to trusted users only via role-based access controls; (2) Implement application sandboxing or containerization with strict resource limits to prevent denial of service impact; (3) Monitor for and block opening of untrusted serialized data files (.pkl, .joblib, etc.) at endpoint level; (4) Maintain isolated network segments for BioNeMo Framework systems; (5) Enable detailed audit logging of file operations and application behavior; (6) Monitor NVIDIA security advisories daily for patch availability.

Threat Intelligence Overview

EPSS Score
0.1%
Top 83% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Insecure deserialization occurs when an application converts serialized data (a stream of bytes representing an object's state) back into a living object without proper validation.

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

Related Vulnerabilities in NVIDIA BioNeMo Deserialization Flaws

View all 2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy