Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. Prior to 1.22.0, _unpack_2bit() and _unpack_4bit() resize unpacked arrays according to attacker-controlled TensorProto.dims without verifying that raw_data or int32_data encodes the declared number of elements. Materializing an untrusted UINT2, INT2, UINT4, INT4, or FLOAT4E2M1 tensor through onnx.numpy_helper.to_array() or onnx.reference.ReferenceEvaluator can therefore expand a small packed payload into a disproportionately large allocation and exhaust memory. This issue is fixed in version 1.22.0.
CVE-2026-115922
MEDIUMPre-NVD 6.26.2Trending — 5 sources updated this week
EchelonGraph scoreHIGH confidence
“—” beside the score: it is equal to the CVSS score beside it.
Score 6.2 from GitHub Security Advisory (severity: MODERATE) published 2026-10-28. A secondary CVSS source baseline 6.2; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Also known asEUVD-2026-110049 (ENISA EUVD) · GHSA-q69g-f4f5-v8m7 (GitHub Security Advisories)Source: ENISA EUVD
6.2EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 6.2Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 6.2
- EG Score
- 6.2MEDIUMhigh confidence
- EG Risk
- 28EG Risk 28/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity62% × 45%Impact severity (EG Severity): CVSS 6.2 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.1% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.1%
- EPSS %ILE
- 2nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (6.2): severity, escalated by confirmed exploitation. This CVE's 6.2 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.2 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 26, 2026
Last Modified
October 30, 2026
Advisory Details (8)
Auto-updated Oct 26, 2026Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available
v1.22.0
Patch available: onnx/onnx v1.22.0
https://github.com/onnx/onnx/releases/tag/v1.22.0GitHub commit
commit dce5876d6cc6 (onnx/onnx)
Fix landed in onnx/onnx commit dce5876d6cc6 — awaiting tagged release
https://github.com/onnx/onnx/commit/dce5876d6cc6cc30157af7d26a752ef44976da8eGitHub commit
commit 8de2cf6aa479 (onnx/onnx)
Fix landed in onnx/onnx commit 8de2cf6aa479 — awaiting tagged release
https://github.com/onnx/onnx/commit/8de2cf6aa47928e6515ac6d9e1a8b4758886a7dfGitHub commit
commit 05c1bc3bcece (onnx/onnx)
Fix landed in onnx/onnx commit 05c1bc3bcece — awaiting tagged release
https://github.com/onnx/onnx/commit/05c1bc3bceceb8d3cf11e9e7fc7f19f971c44988GitHub pull request
Cherrypicks for 1.22.0rc2
Fix merged in onnx/onnx PR #8066 on 2026-06-09 — awaiting tagged release
https://github.com/onnx/onnx/pull/8066GitHub pull request
fix: validate packed sub-byte tensor payload size in checker
Fix merged in onnx/onnx PR #8038 on 2026-06-04 — awaiting tagged release
https://github.com/onnx/onnx/pull/8038GitHub pull request
fix: validate packed tensor dims against payload size in _unpack_4bit and _unpack_2bit
Fix merged in onnx/onnx PR #8033 on 2026-06-04 — awaiting tagged release
https://github.com/onnx/onnx/pull/8033GitHub advisoryMentions a patch (unverified)
Denial of service via unchecked expansion of packed sub-byte tensors in ONNX Python APIs · Advisory · onnx/onnx · GitHub
https://github.com/onnx/onnx/security/advisories/GHSA-q69g-f4f5-v8m7Vendor Advisories for CVE-2026-115922(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| pip | onnx @ 1.22.0 (fixes <= 1.21.0) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| onnx | 0.1 ... 1.9.0 (50 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 13× in last 7d / 13× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-11-01 07:59 UTCGHSA enrichmentGHSA-q69g-f4f5-v8m7 · GitHub severity MODERATE · GitHub CVSS 6.2
- 2026-11-01 07:59 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-30 18:27 UTCEG score recompute
- 2026-10-30 17:45 UTCEG score recompute
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
- 2026-10-26 19:06 UTCEG score recompute
- 2026-10-26 18:01 UTCENISA EUVD ID recordedEUVD-2026-110049 · Source: ENISA EUVD
- 2026-10-26 17:38 UTCEG score recomputeFirst assessed: 6.2 MEDIUM
- 2026-10-26 17:35 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:onnx
Frequently asked(5)
What is CVE-2026-115922?
CVE-2026-115922 is a medium-severity vulnerability; its CVE record was published on October 26, 2026. Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. Prior to 1.22.0, _unpack_2bit() and _unpack_4bit() resize unpacked arrays according to attacker-controlled TensorProto.dims without verifying that raw_data or int32_data encodes the declared number of…
When was the CVE record for CVE-2026-115922 published?
The CVE record for CVE-2026-115922 was published on October 26, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 30, 2026; the record at its source may have been updated since.
Is CVE-2026-115922 actively exploited?
CVE-2026-115922 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-115922?
CVE-2026-115922 has a CVSS base score of 6.2 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-115922?
A fix for CVE-2026-115922 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-115922 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-115922
Is Your Infrastructure Affected by CVE-2026-115922?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.