Home
» GitHub Advisories
» GHSA-v7v2-m736-cf3c
Description
NVIDIA NeMo Framework contains a vulnerability where an attacker may cause remote code execution. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, information disclosure and data tampering.
Basic information
Type
reviewed
Severity
high Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Browse source ↗ Published (advisory)
2026-03-24 21:31:24 UTC
Updated
2026-04-01 23:13:54 UTC
GitHub reviewed
2026-04-01 23:13:53 UTC
NVD published
2026-03-24 21:16:28 UTC
EPSS Score
Score
Percentile
0.10%
27.77%
CVSS Scores
Base score
Version
Severity
Vector
7.8
3.1
—
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
CWEs
CWE id
Name
CWE-502
Deserialization of Untrusted Data
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
Ecosystem
Package
Vulnerable range
First patched
Vulnerable functions
pip
nemo-toolkit < 2.6.2
2.6.2
—
cvelogic
Threat Intelligence