CVE-2026-55093

MEDIUMPre-NVD 6.16.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.1 from GitHub Security Advisory (severity: MODERATE) published 2026-06-18. A secondary CVSS source baseline 6.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-77792 (ENISA EUVD) · GHSA-x5mv-8wgw-29hg (GitHub Security Advisories) · RUSTSEC-2026-0217 (OSV.dev)Source: ENISA EUVD

6.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
6.1
EG Score
6.1MEDIUMmedium confidence
EG Risk
43
EG Risk 43/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)
Severity61% × 45%
Impact severity (EG Severity): CVSS 6.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.2%
EPSS %ILE
7th
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.1): severity, escalated by confirmed exploitation. This CVE's 6.1 is its impact severity (EG Severity), not escalated.

EG Severity
6.1 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% 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 low or medium mission impact; Track* at high (mission-essential systems).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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (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

June 18, 2026

Last Modified

September 30, 2026

Advisory Details (7)

Auto-updated Sep 14, 2026
Patch available. Sources: github, github_commit, github_release.
GitHub release Patch Available

0.23.1

Patch available: sonos/tract v0.23.1

https://github.com/sonos/tract/releases/tag/v0.23.1
GitHub release Patch Available

0.22.2

Patch available: sonos/tract 0.22.2

https://github.com/sonos/tract/releases/tag/0.22.2
GitHub release Patch Available

0.21.16

Patch available: sonos/tract 0.21.16

https://github.com/sonos/tract/releases/tag/0.21.16
GitHub commit

commit ee5f019d39fb (sonos/tract)

Fix landed in sonos/tract commit ee5f019d39fb — awaiting tagged release

https://github.com/sonos/tract/commit/ee5f019d39fb97f7d4431b883c3ce97b74c28a64
GitHub commit

commit 828ec20f74c1 (sonos/tract)

Fix landed in sonos/tract commit 828ec20f74c1 — awaiting tagged release

https://github.com/sonos/tract/commit/828ec20f74c14c0923c7d7f0cff062ed222d630a
GitHub commit

commit 34c7df2c9bd2 (sonos/tract)

Fix landed in sonos/tract commit 34c7df2c9bd2 — awaiting tagged release

https://github.com/sonos/tract/commit/34c7df2c9bd2a36583e09b52f3e6319bf23102e8
GitHub advisoryMentions a patch (unverified)

tract-nnef: integer overflow in NNEF `.dat` tensor parser yields an out-of-bounds read on model load · Advisory · sonos/tract · GitHub

Affected: 0.21.16 / 0.22.2 / 0.23.1

https://github.com/sonos/tract/security/advisories/GHSA-x5mv-8wgw-29hg

Vendor Advisories for CVE-2026-55093(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
rusttract-nnef @ 0.23.1 (fixes >= 0.23.0, < 0.23.1)—ghsa
rusttract-nnef @ 0.22.2 (fixes >= 0.22.0, < 0.22.2)—ghsa
rusttract-nnef @ 0.21.16 (fixes < 0.21.16)—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)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
tract-nnef—
  • 0.23.0 up to 0.23.1: fixed in 0.23.1
  • 0.22.0 up to 0.22.2: fixed in 0.22.2
  • every version up to 0.21.16: fixed in 0.21.16
  • 0.0.0-0 up to 0.21.16: fixed in 0.21.16
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-11-01 07:44 UTCGHSA enrichmentGHSA-x5mv-8wgw-29hg · GitHub severity MODERATE · GitHub CVSS 6.1
  3. 2026-11-01 07:44 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  6. 2026-10-30 11:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-25 14:19 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-22 21:17 UTCEG score recompute
  16. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  19. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-18 03:30 UTCEG score recompute
  21. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  22. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  23. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  24. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  25. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
Show 35 more
  1. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  2. 2026-10-12 15:56 UTCEG score recompute
  3. 2026-10-11 19:39 UTCEG score recompute
  4. 2026-10-11 16:54 UTCEG score recompute
  5. 2026-10-11 14:17 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  7. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  8. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  9. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  10. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  11. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  12. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-30 18:12 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  20. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  21. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  26. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  27. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  29. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-09-14 20:27 UTCEG score recompute
  31. 2026-09-14 20:16 UTCEG score recompute
  32. 2026-07-31 00:46 UTCEG score recompute
  33. 2026-07-26 17:42 UTCEG score recompute
  34. 2026-07-23 03:20 UTCEG score recompute
  35. 2026-06-18 15:07 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55093?
CVE-2026-55093 is a medium-severity vulnerability; its CVE record was published on June 18, 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.…
When was the CVE record for CVE-2026-55093 published?
The CVE record for CVE-2026-55093 was published on June 18, 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 September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-55093 actively exploited?
CVE-2026-55093 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (7th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55093?
CVE-2026-55093 has a CVSS base score of 6.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55093?
A fix for CVE-2026-55093 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55093 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-55093

Explore →

Is Your Infrastructure Affected by CVE-2026-55093?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs