dbcve.org
NvtabularApplication · Nvidia

CVE-2026-24221

HIGH · 7.8 CVSS v3.1 Published 2026-06-02
Fix available
A fix is available. Upgrade to 2026-03-12 or later.
See remediation →
80/100
Remediation priority · High
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 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.

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 NVTabular contains an improper deserialization vulnerability where untrusted data is deserialized without proper validation. This insecure deserialization flaw could allow an attacker to execute arbitrary code, tamper with data, or disclose sensitive information by crafting malicious serialized payloads.

MitigationRestrict deserialization to trusted, authenticated data sources only, implement strict input validation before deserialization, and consider replacing unsafe deserialization methods with safer alternatives such as JSON or validating schema-based formats.

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
NvtabularApplication
Affected:< 2026-03-12

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

CVSS:3.1/AV:L/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 NVTabular version
    Run 'pip show nvt' or 'pip show nvidia-nvtabular' in your environment, or in Python: import nvt; print(nvt.__version__)
    Affected if The version is less than 2026-03-12 (any version before the patched release)
  2. Identify deserialization usage in data pipelines
    Search codebase for pickle.load, pickle.loads, yaml.load (non-safe variants), or similar deserialization functions processing external/input data
    Affected if The pipeline deserializes data from untrusted or external sources without validation (e.g., loading pickle/yaml from user-provided files, APIs, or network sources)
  3. Review data input configurations
    Inspect configuration files and pipeline code that handle data loading from untrusted sources (such as user uploads, external APIs, or shared storage)
    Affected if Data inputs are accepted from untrusted sources and passed directly to deserialization functions without allowlist validation or safe format checks
  4. Audit data pipeline input sources
    Examine where serialized data enters the pipeline: check for HTTP endpoints, file uploads, message queues, or storage paths that accept external data
    Affected if The system accepts serialized data from untrusted or unauthenticated sources

You are affected if NVTabular version is below 2026-03-12 AND your pipeline deserializes data from untrusted or external sources 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-03-12 or later
Fixed in 2026-03-12
Interim mitigation

Restrict deserialization to trusted, authenticated data sources only, implement strict input validation before deserialization, and consider replacing unsafe deserialization methods with safer alternatives such as JSON or validating schema-based formats.

Recommended fix Moderate confidence

Any NVTabular version released on or after 2026-03-12

  1. 1. Identify the current version of NVTabular installed in your environment using pip show nvtabular or conda list nvtabular
  2. 2. Upgrade to a version released on or after 2026-03-12 using: pip install --upgrade nvtabular or conda update nvtabular
  3. 3. Verify the upgrade was successful by running pip show nvtabular and confirming the installed version date is 2026-03-12 or later
  4. 4. Test your workloads to ensure the upgrade does not break existing functionality
Caveat Review NVIDIA's release notes for any breaking changes between your current version and the target version

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

Fix this in Nvtabular Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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