dbcve.org
Bionemo FrameworkApplication · Nvidia

CVE-2026-24165

HIGH · 8.8 CVSS v3.1 Published 2026-03-31
Fix available
A fix is available. Upgrade to 2026-01-21 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 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.

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 · moderate confidence

NVIDIA BioNeMo contains a deserialization vulnerability where untrusted data is deserialized without proper validation. This could allow an attacker to execute arbitrary code, cause denial of service, disclose information, or tamper with data by supplying malicious serialized objects.

MitigationImplement safe deserialization practices such as validating input data, using allowlists for permitted classes, employing JSON/XML instead of binary serialization, or using secure serialization libraries that prevent deserialization of untrusted data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Bionemo FrameworkApplication
Affected:< 2026-01-21

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Check installed BioNeMo Framework version
    Run 'pip show bionemo-framework' or 'pip list | grep -i bionemo' to see the installed version. If using Docker, check the image tag or inspect the container for version labels.
    Affected if The installed version is earlier than 2026-01-21, indicating it is within the affected version range.
  2. Identify deserialization usage in BioNeMo code
    Search the BioNeMo installation directory for deserialization patterns: grep -r 'pickle.load' and 'yaml.load' and 'marshal.load' and 'jsonpickle' and 'shelve' in the codebase.
    Affected if Any model loading, data processing, or configuration loading code uses pickle, yaml, marshal, or similar unsafe deserialization methods without input validation.
  3. Review data input paths that trigger deserialization
    Examine how BioNeMo processes uploaded models, datasets, or configuration files. Look for endpoints or functions that accept serialized data (check for file upload handlers, model loading functions, or data import features).
    Affected if The application accepts serialized data from untrusted sources (user uploads, API requests, external files) without validation before deserialization.
  4. Inspect model loading and inference code
    Review any code that loads pre-trained models or checkpoints, as these often use pickle or joblib for serialization. Check for patterns like 'joblib.load', 'torch.load', 'pickle.load', or 'keras.models.load_model'.
    Affected if Model or checkpoint loading functions use unsafe deserialization without validating the source or content of the serialized data.

You are affected if BioNeMo Framework version is earlier than 2026-01-21 AND the application processes untrusted serialized data through pickle, yaml, or similar deserialization methods without validation.

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.

dbcve · scoped
Upgrade available Upgrade to 2026-01-21 or later
Fixed in 2026-01-21
Interim mitigation

Implement safe deserialization practices such as validating input data, using allowlists for permitted classes, employing JSON/XML instead of binary serialization, or using secure serialization libraries that prevent deserialization of untrusted data.

Recommended fix Moderate confidence

NVIDIA BioNeMo Framework 2026-01-21 or later

  1. 1. Identify the current version of NVIDIA BioNeMo Framework installed in your environment.
  2. 2. Download or access the NVIDIA BioNeMo Framework version 2026-01-21 or later from official NVIDIA sources.
  3. 3. Review the release notes and migration documentation for version 2026-01-21 to understand any required configuration changes.
  4. 4. Create a backup of your current BioNeMo configuration, data, and model files.
  5. 5. Stop all BioNeMo services and running jobs.
  6. 6. Install the upgraded BioNeMo Framework version 2026-01-21 or newer.
  7. 7. Verify the installation by checking the version number matches or exceeds 2026-01-21.
  8. 8. Restart BioNeMo services and confirm normal operation.
Caveat Review release notes for potential breaking changes; specific changes not detailed in provided vulnerability description

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bionemo Framework Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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