CVE-2026-55093
MEDIUMDescription
Tract is a tiny, no-nonsense, self-contained TensorFlow and ONNX inference toolkit. Prior to 0.21.16, 0.22.2, and 0.23.1, tract-nnef uses unchecked usize multiplication in nnef/src/tensors.rs read_tensor for attacker-controlled tensor dimensions, the allocation size, and the reported tensor length. Loading a crafted NNEF archive through model_for_path or model_for_read reaches the default DatLoader and can make the wrapped size check accept a small allocation while data/src/tensor.rs as_slice_unchecked creates a much larger logical slice. Model construction through as_uniform can then read beyond the heap allocation and disclose adjacent data, and later access can terminate the process with a segmentation fault. The affected dense numeric tensor path does not include the independently guarded bool, String, or block-quant paths, and no out-of-bounds write or code execution was demonstrated. This issue is fixed in versions 0.21.16, 0.22.2, and 0.23.1.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 10% of all known CVEs.
References
Related Vulnerabilities
Other CWE-125 (Out-of-bounds Read) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2014-0160 | High | 7.5 | 100% | KEV | Fix |
| CVE-2025-5777 | High | 7.5 | 100% | KEV + Ransom | Fix |
| CVE-2021-4034 | High | 7.8 | 95% | KEV + Ransom | Fix |
| CVE-2020-8794 | Critical | 9.8 | 89% | - | Fix |
| CVE-2023-21769 | High | 7.5 | 89% | - | Fix |
| CVE-2023-49285 | High | 8.6 | 88% | - | Fix |
Common questions
How do I fix CVE-2026-55093?
No published fix for CVE-2026-55093 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-55093 being actively exploited?
Not that we know of. CVE-2026-55093 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.20% is the estimated probability that it will be exploited in the next 30 days. That is higher than 10% of all scored CVEs.
How severe is CVE-2026-55093?
CVE-2026-55093 has a CVSS v3 base score of 6.1, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-55093
Markdown
[](https://tridentstack.com/cve/CVE-2026-55093)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55093"><img src="https://tridentstack.com/cve/badge/CVE-2026-55093.svg" alt="CVE-2026-55093"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-14.