# CVE-2026-55832: Tract: Arbitrary file read via unsanitized ONNX external_data `location` (path traversal) on model load in tract-onnx

> Attackers can read arbitrary local files or cause denial of service by loading a malicious ONNX model with crafted external data locations in tract-onnx.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-h668-6x6g-f8r5

## What is CVE-2026-55832?

CVE-2026-55832 is a medium-severity path traversal vulnerability in sonos tract, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Tract is a tiny, no-nonsense, self-contained TensorFlow and ONNX inference toolkit. Prior to 0.21.17, 0.22.3, and 0.23.2, the tract-onnx crate passes the attacker-controlled external_data location from an ONNX model through onnx/src/tensor.rs get_external_resources and joins the value to the model directory without rejecting absolute paths or parent directory components. Loading an untrusted model through model_for_path can therefore make onnx/src/data_resolver.rs MmapDataResolver open an arbitrary local file and place the file contents into model tensors or inference output. Attacker-controlled offset and length fields can also select an out-of-range mapping slice and cause a denial of service, but the flaw does not write files or execute code. This issue is fixed in versions 0.21.17, 0.22.3, and 0.23.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

6 open source packages ship an affected version, including tract-onnx.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tract-onnx` | crates.io | All versions | 0.21.17 |
| `tract-onnx` | crates.io | All versions | 0.21.17 |
| `tract-onnx` | crates.io | From 0.22.0 | 0.22.3 |
| `tract-onnx` | crates.io | From 0.22.0 | 0.22.3 |
| `tract-onnx` | crates.io | From 0.23.0 | 0.23.2 |
| `tract-onnx` | crates.io | From 0.23.0 | 0.23.2 |

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

Upgrade tract-onnx to a fixed version for your release line: 0.21.17, 0.22.3 or 0.23.2.

## Is CVE-2026-55832 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55832 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55832 is a medium-severity path traversal vulnerability in sonos tract, published on 14 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55832 exists.

Affected packages and fixed versions:
- tract-onnx (crates.io): affected all versions; fixed in 0.21.17
- tract-onnx (crates.io): affected all versions; fixed in 0.21.17
- tract-onnx (crates.io): affected from 0.22.0; fixed in 0.22.3
- tract-onnx (crates.io): affected from 0.22.0; fixed in 0.22.3
- tract-onnx (crates.io): affected from 0.23.0; fixed in 0.23.2
- tract-onnx (crates.io): affected from 0.23.0; fixed in 0.23.2

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-55832/ (Markdown: https://insights.sbomify.com/CVE-2026-55832/index.md)
```

## Sources

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

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