Local code execution via unsafe ONNX deserialization
Published Mar 24, 2026 · Updated Mar 24, 2026
Unsafe deserialization in NVIDIA Model Optimizer before 0.41.0 allows local users to execute code through a crafted ONNX input file. The ONNX quantization feature deserializes attacker-controlled content, but NVIDIA has not disclosed the responsible parser, function, or unsafe call. Exploitation requires a user to process the crafted file and runs code with that user's privileges, enabling data access, modification, or service interruption.
Summary
What happened
Unsafe deserialization in NVIDIA Model Optimizer before 0.41.0 allows local users to execute code through a crafted ONNX input file. The ONNX quantization feature deserializes attacker-controlled content, but NVIDIA has not disclosed the responsible parser, function, or unsafe call. Exploitation requires a user to process the crafted file and runs code with that user's privileges, enabling data access, modification, or service interruption.
The record
- CVE
- CVE-2026-24141
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- DPDK Project
- Product
- NVIDIA Model Optimizer
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 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=All versions prior to 0.41.0
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