CVE-2026-44512: ONNX Null Pointer Denial of Service in Version Converter
ONNX (Open Neural Network Exchange), a widely-used standard for sharing machine learning models across frameworks, contains a vulnerability in its version converter tool. When this tool processes a specially crafted model file—specifically one with an Upsample component that lacks the required inputs—the software crashes due to a null pointer dereference. An attacker can exploit this by distributing a malicious model file; anyone who attempts to convert it using affected ONNX versions will experience a denial-of-service condition. The vulnerability affects ONNX versions 1.9.0 through 1.21.x and is resolved in version 1.22.0.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.5 MEDIUM · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses (CWE)
- CWE-476
- Affected products
- 1 configuration(s)
- Published / Modified
- 2026-07-08 / 2026-07-13
NVD description (verbatim)
Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. From 1.9.0 before 1.22.0, onnx.version_converter.convert_version() can dereference a null pointer in Upsample_6_7::adapt_upsample_6_7() in onnx/version_converter/adapters/upsample_6_7.h when processing an untrusted model with an Upsample node that has zero inputs, causing an unrecoverable denial of service. This issue is fixed in version 1.22.0.
5 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the version_converter.convert_version() function within onnx/version_converter/adapters/upsample_6_7.h. When processing an Upsample node (version 6/7) that has been malformed to contain zero inputs, the adapt_upsample_6_7() function attempts to dereference a null pointer without proper validation. This results in a segmentation fault or equivalent unrecoverable crash condition. The issue is triggered during the model conversion process, which is commonly used when importing models across different ONNX opset versions. The null pointer dereference (CWE-476) indicates inadequate input validation before pointer dereference operations.
Business impact
Organizations developing, training, or deploying machine learning models using ONNX are at risk. ML engineers or automated pipelines that consume externally sourced models—whether from model repositories, third-party vendors, or research collaborations—can be disrupted if a malicious model is introduced. The impact is availability-focused: services that depend on model conversion workflows will become unavailable until the process can be restarted, potentially delaying model deployment, retraining, or inference pipeline updates. For organizations relying on continuous integration/continuous deployment (CI/CD) workflows that include model conversion, this could trigger cascading delays.
Affected systems
ONNX versions 1.9.0 through 1.21.x are vulnerable. The Linux Foundation maintains the ONNX project. Any system running a vulnerable version of the ONNX library—whether standalone or as a dependency embedded in other tools—is affected. This includes development workstations, CI/CD pipelines, model conversion services, and any ML framework integration that internally uses ONNX's version converter. The vulnerability does not require network access; it is triggered by file-based processing.
Exploitability
Exploitation requires convincing a user or automated system to process an untrusted model file using onnx.version_converter.convert_version(). The attacker's crafted model must contain a malformed Upsample node with zero inputs. While this is not a remote code execution vulnerability, the low barrier to entry—creating a malicious model file and distributing it via email, research repositories, or model sharing platforms—combined with the common practice of importing models from external sources, makes this a realistic attack vector. No special privileges are required, and user interaction is minimal (simply attempting to convert the model). However, the vulnerability is not currently in the CISA Known Exploited Vulnerabilities (KEV) catalog, suggesting limited real-world exploitation to date.
Remediation
Upgrade ONNX to version 1.22.0 or later. This is a straightforward patch for most deployments. Organizations should prioritize this update for any system or service involved in model conversion, particularly those that accept externally sourced models. For environments where immediate patching is not feasible, implementing input validation or sandboxing model conversion operations can reduce risk. Additionally, organizations should audit which tools and frameworks depend on ONNX and verify their versions have been updated accordingly, since ONNX is often a transitive dependency.
Patch guidance
Verify compatibility of ONNX 1.22.0 with downstream frameworks and tools in your environment before full rollout. The patch addresses the null pointer dereference in the Upsample adapter without reported breaking changes, but regression testing against your organization's model conversion pipelines is recommended. Update package managers (pip, conda, apt, etc.) to pull the latest version. For containerized deployments, rebuild container images with the updated ONNX library. For embedded or vendored copies of ONNX, ensure build systems pull from patched source versions.
Detection guidance
Monitor logs for segmentation faults or unhandled exceptions in ONNX conversion processes, particularly for any crashes involving upsample_6_7.h or version_converter components. In automated workflows, track conversion job failures correlated with new or recently-added model files. Network-based detection is limited since the vulnerability is triggered by file processing; focus on endpoint monitoring. Examine model files introduced to your environment for suspicious characteristics (malformed operator definitions, missing required node inputs). Vulnerability scanning tools should flag ONNX library versions below 1.22.0 in dependency inventories.
Why prioritize this
While this is a medium-severity vulnerability with limited real-world exploitation, it poses a direct risk to organizations that ingest external ML models. The ease of exploitation—requiring only a malformed file—and the prevalence of ONNX in ML ecosystems make this a worthwhile near-term target for patching. The lack of confidentiality or integrity impact and the requirement for user/automation interaction to process the file prevent a higher rating, but availability disruption in ML pipelines can have downstream business consequences. Organizations with active model development and integration workflows should prioritize this; research teams or those using curated internal models face lower risk.
Risk score, explained
CVSS 3.1 score of 5.5 (MEDIUM) reflects: attack vector as local (files must be processed locally), low complexity, no privilege escalation required, user interaction needed (someone must attempt conversion), and high availability impact (complete denial of service for the conversion process). The score appropriately weighs the lack of data confidentiality or integrity risk against the complete availability impact. The real-world risk depends on your organization's exposure to external models and the criticality of conversion pipelines.
Frequently asked questions
Can this vulnerability be exploited remotely over the network?
No. The vulnerability is triggered when a local system processes a malicious model file using ONNX's version converter. An attacker would need to convince someone to download and convert the file, or introduce it into a shared model repository. There is no remote attack surface.
What happens when the vulnerability is triggered?
The ONNX conversion process crashes with a null pointer dereference, halting the conversion job and potentially disrupting any downstream workflows that depend on it. The process cannot recover and must be restarted. This is a denial-of-service condition, not data theft or system compromise.
How do I know if my ML pipeline uses ONNX?
Check your project dependencies. If using frameworks like PyTorch, TensorFlow, or Scikit-learn with ONNX export/import capabilities, or if you explicitly imported onnx, you are affected. Run pip show onnx or conda list onnx to check installed version. Also check transitive dependencies in requirements.txt or setup.py for any 'onnx' reference.
Is there a workaround if I cannot immediately patch?
Temporarily restrict model conversions to internally validated models with known-good structure, or sandbox conversion operations in isolated environments. Implement file validation to reject models with malformed operator definitions before attempting conversion. However, these are interim measures; patching to 1.22.0 is the permanent solution.
This analysis is provided for informational purposes and reflects publicly available vulnerability data as of the publication date. Security assessments should be tailored to your organization's specific environment, dependencies, and risk tolerance. Verify all patch version information against official vendor advisories before deployment. This vulnerability does not appear in active exploit databases at publication; however, absence from known exploit lists does not guarantee immunity from exploitation. Organizations should conduct their own testing and validation before applying patches to production systems. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-58250HIGHNATS Server Leafnode Compression Denial of Service
- CVE-2025-55639MEDIUMGPAC MP4Box NULL Pointer Dereference Denial of Service
- CVE-2025-55641MEDIUMNULL Pointer Dereference in GPAC MP4Box v2.4 Denial of Service
- CVE-2025-55643MEDIUMGPAC MP4Box NULL Pointer DoS Vulnerability
- CVE-2025-55649MEDIUMGPAC MP4Box NULL Pointer DoS Vulnerability
- CVE-2025-55651MEDIUMGPAC MP4Box NULL Pointer Dereference DoS Vulnerability
- CVE-2025-55659MEDIUMGPAC MP4Box NULL Pointer Denial of Service
- CVE-2025-55663MEDIUMMP4Box Segmentation Fault DoS Vulnerability – GPAC v2.4