CVE-2026-24164 is a high severity (CVSS 8.8) deserialization of untrusted data flaw in NVIDIA BioNeMo Framework on Linux. NVIDIA's fix is commit e5e58c8. Any version or branch that does not include that commit is affected, so update to a code branch that contains it.
What's affected
NVIDIA's March 2026 BioNeMo bulletin says all versions that do not include commit e5e58c8 are affected. The updated version is any code branch that includes that commit. There is no single release number in the bulletin, so you have to check by commit.
The CVSS vector is network based, needs no privileges and needs user interaction. NVIDIA lists code execution, denial of service, information disclosure and data tampering as possible impacts.
How to check if you're exposed
If you track BioNeMo from source, ask git whether your checkout contains the fix:
git merge-base --is-ancestor e5e58c8 HEAD && echo fixed || echo not fixed
If you run a packaged or containerized build, check with whoever produced it which commit it was built from. When that is unclear, treat the build as unpatched and rebuild from a branch that includes the commit.
For a quick look at your own dependencies, Safeguard's free in-browser dependency scan at https://gold.safeguard.sh/scan checks them against known CVEs in your browser.
What to do now
- Pull a BioNeMo code branch that includes commit e5e58c8.
- Rebuild images and notebooks environments from that source.
- Do not load model files, checkpoints or data from sources you do not control until you are patched.
- Inventory every place BioNeMo runs, including research workstations.
Why it matters
The class is CWE-502. When a program deserializes data from an untrusted source, the data can decide which objects get built, and that can end in code execution. ML tooling is a common place for this because models and checkpoints are often shared as serialized files.
The vector needs user interaction, so the realistic path is a person opening or loading something an attacker prepared. Treat shared model artifacts the way you treat any downloaded executable. The CVE is not in CISA's Known Exploited Vulnerabilities catalog.
Quick check
How do I know if I have the fix?
Check whether your source tree includes commit e5e58c8. NVIDIA defines the fix by that commit, not by a version number.
Does the CVE need user interaction?
Yes. The CVSS vector sets user interaction to required.
Sources
Last reviewed: 19 October 2026.