CVE-2026-24141
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 · uneditedNVIDIA Model Optimizer for Windows and Linux contains a vulnerability in the ONNX quantization feature, where a user could cause unsafe deserialization by providing a specially crafted input file. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, 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 · high confidenceNVIDIA Model Optimizer contains an unsafe deserialization vulnerability in its ONNX quantization feature. By providing a specially crafted malicious ONNX input file, an attacker can trigger unsafe deserialization, potentially achieving code execution, privilege escalation, data tampering, or information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check if NVIDIA Model Optimizer is installedLocate the model optimizer installation by searching for 'model_optimizer', 'mo', or 'optimizer' in common Python package locations. Run: pip list | grep -i model_optimizer or pip show nvidia-model-optimizerAffected if NVIDIA Model Optimizer package is not found in the environment
-
Determine the installed version of NVIDIA Model OptimizerRun: pip show nvidia-model-optimizer or python -c 'import nvidia.model_optimizer; print(nvidia.model_optimizer.__version__)'Affected if The installed version falls within any affected version range or cannot be determined (treat unknown versions as potentially vulnerable)
-
Verify if ONNX quantization feature is in useSearch project code, scripts, or configuration files for references to 'quantization', 'onnx quantization', or calls to quantization-related functions or commands. Inspect any pipeline configuration that loads or processes ONNX files.Affected if ONNX quantization is invoked or configured to process ONNX input files
-
Inspect input handling for ONNX filesReview how ONNX files are loaded in the quantization workflow. Check if there is validation on ONNX files before they are passed to the quantization feature.Affected if ONNX files from untrusted sources are processed without validation or verification steps
The environment is affected if NVIDIA Model Optimizer is installed, the ONNX quantization feature is used, and untrusted or unverified ONNX files can be processed by that feature.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataAvoid processing untrusted or unverified ONNX files with the quantization feature until an official patch is available. Implement strict input validation and consider sandboxing quantization operations.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24141 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24141 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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