# CVE-2026-34445: ONNX: Malicious ONNX models can crash servers by exploiting unprotected object settings.

> Attackers can crash servers by uploading malicious ONNX models that overwrite internal object properties via unprotected setattr calls.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** AZL-81989, DEBIAN-CVE-2026-34445, ECHO-a26a-b5fe-3ab2, GHSA-538c-55jv-c5g9, PYSEC-2026-2240, UBUNTU-CVE-2026-34445

## What is CVE-2026-34445?

CVE-2026-34445 is a high-severity vulnerability in onnx, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. Prior to version 1.21.0, the ExternalDataInfo class in ONNX was using Python’s setattr() function to load metadata (like file paths or data lengths) directly from an ONNX model file. It didn’t check if the "keys" in the file were valid. Due to this, an attacker could craft a malicious model that overwrites internal object properties. This issue has been patched in version 1.21.0.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-400 (Uncontrolled Resource Consumption), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-34445?

3 open source packages ship an affected version, including onnx. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `onnx` | PyPI | All versions | 1.21.0 |
| `onnx` | PyPI | All versions | 1.21.0 |
| `onnx` | PyPI | All versions | 1.21.0 |

Products: Linuxfoundation Onnx.

## How do I fix CVE-2026-34445?

Upgrade onnx to 1.21.0 or later.

## Is CVE-2026-34445 being exploited?

There is no known exploitation of CVE-2026-34445 in the wild and no public exploit code.

## Other vulnerabilities in onnx

- [CVE-2025-51480](https://insights.sbomify.com/CVE-2025-51480/): Path traversal in n/a (high 8.8)
- [CVE-2024-5187](https://insights.sbomify.com/CVE-2024-5187/): Arbitrary File Overwrite in download_model_with_test_data in onnx/onnx (high 8.8)
- [CVE-2026-27489](https://insights.sbomify.com/CVE-2026-27489/): ONNX: Path Traversal via Symlink (high 8.7)
- [CVE-2026-28500](https://insights.sbomify.com/CVE-2026-28500/): ONNX Untrusted Model Repository Warnings Suppressed by silent=True in onnx.hub.load() — Silent Supply-Chain Attack (high 8.6)
- [CVE-2022-25882](https://insights.sbomify.com/CVE-2022-25882/): Directory Traversal in onnx (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-34445 and fix it if it is affected.

What it is: CVE-2026-34445 is a high-severity vulnerability in onnx, published on 1 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-34445 in the wild and no public exploit code.

Affected packages and fixed versions:
- onnx (PyPI): affected all versions; fixed in 1.21.0
- onnx (PyPI): affected all versions; fixed in 1.21.0
- onnx (PyPI): affected all versions; fixed in 1.21.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-34445/ (Markdown: https://insights.sbomify.com/CVE-2026-34445/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-34445
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-34445
- OSV: https://osv.dev/vulnerability/CVE-2026-34445

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-34445/
Summaries are generated and may contain mistakes; the official description above is the record.