Quick answers
- Is CVE-2026-115922 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-115922 being exploited in the wild.
- How severe is CVE-2026-115922?
- Medium severity, with a CVSS score of 6.2, published 26 October 2026.
- Which products and versions are affected?
- ONNX before 1.22.0; onnx (PyPI) <= 1.21.0, ECOSYSTEM:introduced=0,fixed=1.22.0.
- Is there a fix for CVE-2026-115922?
- Yes. onnx (PyPI): upgrade to 1.22.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-115922 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-115922?
- Check whether you run ONNX or onnx (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- onnx (PyPI): upgrade to 1.22.0 or later
pip install "onnx>=1.22.0"
Technical details
The _unpack_2bit() and _unpack_4bit() functions in ONNX fail to validate that raw_data or int32_data fields contain sufficient bytes to match the declared tensor dimensions. An attacker can craft a TensorProto with small payload but large declared element count, causing the numpy_helper.to_array() or ReferenceEvaluator materialisation code to allocate disproportionately large memory. The vulnerability affects UINT2, INT2, UINT4, INT4, and FLOAT4E2M1 tensor types.
Affected products
- ONNX ONNX before 1.22.0
Identifiers
- CVE-2026-115922
- GHSA-q69g-f4f5-v8m7
Timeline
- 2026-10-26: disclosed