dbcve.org
NvtabularApplication · Nvidia

CVE-2026-24237

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 serialized data is deserialized without adequate validation. This type of flaw can allow attackers to craft malicious payloads that execute arbitrary code, manipulate data, or expose sensitive information during the deserialization process.

MitigationAvoid deserializing untrusted data; implement strict type allowlists for deserialization; validate all input before processing; consider migrating to safer serialization formats like JSON.

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. Identify NVTabular installation and version
    Run 'pip show nvt' or 'pip show nvtabular' to retrieve the installed package version and compare the version date to 2026-03-12
    Affected if The installed version date is before 2026-03-12, meaning the patch has not been applied
  2. Locate deserialization code in NVTabular
    Search source files for usage of pickle.load, pickle.loads, yaml.load, or similar deserialization functions without SafeLoader parameters
    Affected if The codebase contains deserialization logic that processes untrusted input using unsafe formats like pickle
  3. Inspect data intake pipelines for serialized input
    Examine NVTabular workflow configuration files or data loading code for operations that accept serialized objects from external or untrusted sources
    Affected if NVTabular is configured to deserialize data from untrusted or network-accessible sources without validation
  4. Check for user-controlled input deserialization
    Review API endpoints or data ingestion points where users can supply serialized data to NVTabular processing
    Affected if The application accepts serialized data from users or external systems without integrity or allowlist validation
  5. Audit custom model or workflow loading mechanisms
    Inspect any custom model loading or workflow import functionality for deserialization of user-supplied or remotely-fetched objects
    Affected if Workflows or models are loaded from locations controlled by untrusted parties using unsafe deserialization

You are affected if NVTabular is installed with a version date before 2026-03-12 and the application deserializes data from untrusted or external sources using unsafe formats like pickle 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

Avoid deserializing untrusted data; implement strict type allowlists for deserialization; validate all input before processing; consider migrating to safer serialization formats like JSON.

Recommended fix Moderate confidence

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

  1. 1. Identify the current NVTabular version installed in your environment using 'pip show nvtabular' or checking your dependency files
  2. 2. Confirm the installed version is earlier than the 2026-03-12 release
  3. 3. Review your project dependencies to identify all locations where NVTabular is specified
  4. 4. Update NVTabular dependency to a version released on or after 2026-03-12 using 'pip install --upgrade nvtabular' or by updating your requirements.txt/environment configuration
  5. 5. Test the upgraded version in a non-production environment to verify compatibility with your existing workflows
  6. 6. Deploy the updated version to production after successful validation
Caveat Review release notes for potential breaking changes between your current version and the target version, particularly related to API changes or dependency requirements

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

Fix this in Nvtabular Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
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,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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