# CVE-2026-11329: onnx onnx-mlir Placeholder Node Cache backend.py generate_hash_key weak hash

> A weak hash implementation in the ONNX MLIR placeholder node cache allows local attackers to potentially bypass security checks due to predictable hash values.

- **Severity:** Low 2.0 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-h7gg-9w38-vh5g

## What is CVE-2026-11329?

CVE-2026-11329 is a low-severity vulnerability in onnx-mlir, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been found in onnx onnx-mlir up to 0.5.0.0. Affected by this issue is the function generate_hash_key of the file src/Runtime/python/torch_onnxmlir/src/torch_onnxmlir/backend.py of the component Placeholder Node Cache Handler. Such manipulation leads to use of weak hash. An attack has to be approached locally. A high complexity level is associated with this attack. The exploitation is known to be difficult. The name of the patch is 72c5187ff6d13c2c2b3d3789b8f5faf99f08a5b4. Applying a patch is advised to resolve this issue.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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


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

No fix has been published for CVE-2026-11329 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11329 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11329 is a low-severity vulnerability in onnx-mlir, published on 5 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-11329 in the wild and no public exploit code.

Affected product: onnx-mlir. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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