Local code execution via cloudpickle workflow loading
Published Jun 2, 2026 · Updated Jun 2, 2026
Improper deserialization in NVIDIA NVTabular through commit 5dd11f4 allows local users to execute code by loading a crafted workflow. The vulnerable Workflow.load path passes serialized workflow data to cloudpickle, which reconstructs attacker-controlled Python objects without a safe data-only boundary. Low-privileged local access and control of a workflow artifact are required; execution occurs in the loading process and also permits data reads, writes, or a crash.
Summary
What happened
Improper deserialization in NVIDIA NVTabular through commit 5dd11f4 allows local users to execute code by loading a crafted workflow. The vulnerable Workflow.load path passes serialized workflow data to cloudpickle, which reconstructs attacker-controlled Python objects without a safe data-only boundary. Low-privileged local access and control of a workflow artifact are required; execution occurs in the loading process and also permits data reads, writes, or a crash.
The record
- CVE
- CVE-2026-24237
- Published
- Jun 2, 2026
- Updated
- Jun 2, 2026
- Vendor
- DPDK Project
- Product
- NVTabular
- Classifications
- CWE-502, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 2, 2026CVE publishedPublication date reported by the CVE source.
- Jun 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.0 to 5dd11f4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo