CVE-2026-24221: NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted
CVE-2026-24221 is a high-severity flaw (CVSS 7.8) affecting nvtabular. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering and information disclosure.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.8 (High) |
| Attack vector | Local |
| Attack complexity | Low |
| Privileges needed | Low |
| User interaction | None |
| EPSS exploit chance | 0.2% (top 94%) |
| CISA exploited list | No |
| Weakness | CWE-502 |
| Published | 2026-06-02 |
| Last modified | 2026-07-22 |
Last updated 2026-07-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-24221?
nvtabular: upgrade to 2026-03-12. Exact commands for each OS are on this page.
Is CVE-2026-24221 being exploited?
CVE-2026-24221 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-24221 affect?
CVE-2026-24221 affects nvtabular. Severity is high (CVSS 7.8). NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, data tampering and information disclosure.
How urgent is CVE-2026-24221?
Priority 29/100. High severity
Software pages
Related CVEs
- CVE-2026-24237 HIGH 7.8 UPGRADE NVIDIA NVTabular contains a vulnerability where an attacker could cause improper deserialization of untrusted