Answer in brief
CVE-2026-55093 records a Medium severity (CVSS 6.1) vulnerability in tract-nnef: integer overflow in NNEF `.dat` tensor parser yields an out-of-bounds read on model load. The current sources do not mark it as known exploited. The current feed maps sonos/tract (generic), tract-nnef (rust), tract-nnef (rust), tract-nnef (rust). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps sonos/tract (generic), tract-nnef (rust), tract-nnef (rust), tract-nnef (rust). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| sonos/tractgeneric | <0.21.16 || >=0.22.0 <0.22.2 || >=0.23.0 <0.23.1 | 0.21.16, 0.22.2, 0.23.1 |
| tract-nnefrust | >=0.23.0,<0.23.1 | 0.23.1 |
| tract-nnefrust | >=0.22.0,<0.22.2 | 0.22.2 |
| tract-nnefrust | <0.21.16 | 0.21.16 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 19, 2026
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.
Quoted source text, attributed separately from HOL analysis.