CVE-2026-28500

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.4% (29th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.6 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-03-16) is not newer than that change (2026-07-15), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-12698 (ENISA EUVD) · GHSA-hqmj-h5c6-369m (GitHub Security Advisories) · PYSEC-2026-103 (OSV.dev)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.4%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. In versions up to and including 1.20.1, a security control bypass exists in onnx.hub.load() due to improper logic in the repository trust verification mechanism. While the function is designed to warn users when loading models from non-official sources, the use of the silent=True parameter completely suppresses all security warnings and confirmation prompts. This vulnerability transforms a standard model-loading function into a vector for Zero-Interaction Supply-Chain Attacks. When chained with file-system vulnerabilities, an attacker can silently exfiltrate sensitive files (SSH keys, cloud credentials) from the victim's machine the moment the model is loaded. As of time of publication, no known patched versions are available.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
29th
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

March 16, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Patch available. Sources: github, redhat.
Web page

CVEs/2026/CVE-2026-28500.md at main · ZeroXJacks/CVEs · GitHub

https://github.com/ZeroXJacks/CVEs/blob/main/2026/CVE-2026-28500.md
Red Hat

2448518 – (CVE-2026-28500) CVE-2026-28500 onnx: ONNX: Untrusted Model Repository Warnings Suppressed

https://bugzilla.redhat.com/show_bug.cgi?id=2448518
Red HatMentions a patch (unverified)

CVE-2026-28500 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-28500
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:24977
GitHub advisoryMentions a patch (unverified)

Trust Check Bypass in onnx.hub.load() via silent=True · Advisory · onnx/onnx · GitHub

https://github.com/onnx/onnx/security/advisories/GHSA-hqmj-h5c6-369m

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17902609542026-09-30redhat
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17800692222026-06-10redhat
piponnx @ 1.21.0rc1 (fixes <= 1.20.1)—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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
onnx1.12.0-1 ... 1.7.0+dfsg-3.1 (24 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
onnx1.12.0-2 ... 1.21.0-1 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
onnx1.17.0-3 ... 1.21.0-1 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
onnx1.17.0-3 ... 1.21.0-1 (9 versions)
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
onnx0.1 ... 1.9.0 (43 versions)
  • every version up to 1.21.0rc1: fixed in 1.21.0rc1
—

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 21× in last 7d / 73× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 309 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 209 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-13 16:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  2. 2026-11-13 14:24 UTCEchelonGraph re-scored
  3. 2026-11-13 14:24 UTCVendor advisory
  4. 2026-11-13 14:24 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  5. 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-11-12 13:51 UTCEchelonGraph re-scored
  7. 2026-11-12 13:51 UTCVendor advisory
  8. 2026-11-12 13:51 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  9. 2026-11-11 16:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-11-11 13:19 UTCEchelonGraph re-scored
  11. 2026-11-11 13:19 UTCVendor advisory
  12. 2026-11-11 13:19 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  13. 2026-11-10 16:43 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-11-10 12:47 UTCEchelonGraph re-scored
  15. 2026-11-10 12:47 UTCVendor advisory
  16. 2026-11-10 12:47 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  17. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-11-09 12:15 UTCEchelonGraph re-scored
  19. 2026-11-09 12:15 UTCVendor advisory
  20. 2026-11-09 12:14 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  21. 2026-11-08 16:39 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-11-08 11:42 UTCEchelonGraph re-scored
  23. 2026-11-08 11:42 UTCVendor advisory
  24. 2026-11-08 11:42 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  25. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 75 more
  1. 2026-11-07 11:11 UTCEchelonGraph re-scored
  2. 2026-11-07 11:11 UTCVendor advisory
  3. 2026-11-07 11:11 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  4. 2026-11-06 16:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-11-06 10:39 UTCEchelonGraph re-scored
  6. 2026-11-06 10:39 UTCVendor advisory
  7. 2026-11-06 10:39 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  8. 2026-11-06 04:55 UTCOSV refresh
  9. 2026-11-05 16:37 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  10. 2026-11-05 10:08 UTCEchelonGraph re-scored
  11. 2026-11-05 10:08 UTCVendor advisory
  12. 2026-11-05 10:08 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  13. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  14. 2026-11-04 09:32 UTCEchelonGraph re-scored
  15. 2026-11-04 09:32 UTCVendor advisory
  16. 2026-11-04 09:32 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  17. 2026-11-03 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-11-03 09:00 UTCEchelonGraph re-scored
  19. 2026-11-03 09:00 UTCVendor advisory
  20. 2026-11-03 09:00 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  21. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-11-02 08:28 UTCEchelonGraph re-scored
  23. 2026-11-02 08:28 UTCVendor advisory
  24. 2026-11-02 08:28 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  25. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-11-01 07:56 UTCVendor advisory
  27. 2026-11-01 07:56 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  28. 2026-11-01 07:55 UTCGHSA enrichmentGHSA-hqmj-h5c6-369m · GitHub severity HIGH · GitHub CVSS 8.6
  29. 2026-11-01 07:55 UTCEchelonGraph re-scored
  30. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-10-31 07:24 UTCEchelonGraph re-scored
  32. 2026-10-31 07:24 UTCVendor advisory
  33. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  34. 2026-10-30 06:52 UTCEchelonGraph re-scored
  35. 2026-10-30 06:52 UTCVendor advisory
  36. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  37. 2026-10-29 06:20 UTCEchelonGraph re-scored
  38. 2026-10-29 06:20 UTCVendor advisory
  39. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  40. 2026-10-28 05:48 UTCEchelonGraph re-scored
  41. 2026-10-28 05:48 UTCVendor advisory
  42. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  43. 2026-10-27 05:17 UTCEchelonGraph re-scored
  44. 2026-10-27 05:17 UTCVendor advisory
  45. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-10-26 00:43 UTCEchelonGraph re-scored
  47. 2026-10-26 00:43 UTCVendor advisory
  48. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-10-25 14:38 UTCEchelonGraph re-scored
  50. 2026-10-25 00:08 UTCEchelonGraph re-scored
  51. 2026-10-25 00:08 UTCVendor advisory
  52. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-10-23 23:36 UTCEchelonGraph re-scored
  54. 2026-10-23 23:36 UTCVendor advisory
  55. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  56. 2026-10-22 22:56 UTCEchelonGraph re-scored
  57. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-10-21 22:25 UTCEchelonGraph re-scored
  59. 2026-10-21 22:25 UTCVendor advisory
  60. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-10-20 21:51 UTCEchelonGraph re-scored
  62. 2026-10-20 21:51 UTCVendor advisory
  63. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  64. 2026-10-19 21:20 UTCEchelonGraph re-scored
  65. 2026-10-19 21:20 UTCVendor advisory
  66. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-10-18 20:25 UTCEchelonGraph re-scored
  68. 2026-10-18 20:25 UTCVendor advisory
  69. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-10-18 03:50 UTCEchelonGraph re-scored
  71. 2026-10-17 19:51 UTCEchelonGraph re-scored
  72. 2026-10-17 19:51 UTCVendor advisory
  73. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  74. 2026-10-16 19:18 UTCEchelonGraph re-scored
  75. 2026-10-16 19:18 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-28500?
CVE-2026-28500 is a critical-severity vulnerability; its CVE record was published on March 16, 2026. Open Neural Network Exchange (ONNX) is an open standard for machine learning interoperability. In versions up to and including 1.20.1, a security control bypass exists in onnx.hub.load() due to improper logic in the repository trust verification mechanism. While the function is designed to warn…
When was the CVE record for CVE-2026-28500 published?
The CVE record for CVE-2026-28500 was published on March 16, 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 July 15, 2026; the record at its source may have been updated since.
Is CVE-2026-28500 actively exploited?
CVE-2026-28500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-28500?
CVE-2026-28500 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-28500?
A fix for CVE-2026-28500 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-28500 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-28500

Explore →

Is Your Infrastructure Affected by CVE-2026-28500?

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