CVE-2026-28500

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this weekElevated
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.1Exploit: Elevated riskExposed: 0

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.1(medium)
EG Risk
72(Attend)
EG Risk 72/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity91% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

March 16, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Aug 1, 2026
Patch available. Sources: github, redhat.
generic

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

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

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

https://bugzilla.redhat.com/show_bug.cgi?id=2448518
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-28500
github Patch Available

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

Vendor Advisories for CVE-2026-28500(2)

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 / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17800692222026-06-10redhat

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 rangeFixed inDependents
onnx1.12.0-1 ... 1.7.0+dfsg-3.1 (24 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
onnx1.12.0-2 ... 1.20.0-6 (20 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
onnx1.17.0-3 ... 1.20.0-6 (8 versions)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
onnx1.17.0-3 ... 1.20.0-6 (8 versions)
PyPI(1)
PackageVulnerable rangeFixed inDependents
onnx0.1 ... 1.9.0 (43 versions)1.21.0rc1

Weakness Classification(4)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 72× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 147 total refreshes for this CVE.

  1. 2026-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 11:24 UTCEG score recompute
  8. 2026-08-16 11:24 UTCVendor advisory
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 23:59 UTCVendor advisory
  12. 2026-08-14 19:59 UTCVendor advisory
  13. 2026-08-14 15:32 UTCVendor advisory
  14. 2026-08-14 11:31 UTCVendor advisory
  15. 2026-08-14 07:30 UTCEG score recompute
  16. 2026-08-14 07:30 UTCVendor advisory
  17. 2026-08-13 22:00 UTCEPSS rescore
  18. 2026-08-13 02:18 UTCVendor advisory
  19. 2026-08-12 22:18 UTCEG score recompute
  20. 2026-08-12 22:18 UTCVendor advisory
  21. 2026-08-12 13:50 UTCEPSS rescore
  22. 2026-08-12 01:35 UTCVendor advisory
  23. 2026-08-11 21:35 UTCEG score recompute
  24. 2026-08-11 21:35 UTCVendor advisory
  25. 2026-08-11 13:42 UTCEPSS rescore
Show 75 more
  1. 2026-08-11 08:43 UTCVendor advisory
  2. 2026-08-11 04:42 UTCEG score recompute
  3. 2026-08-11 04:42 UTCVendor advisory
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 09:27 UTCVendor advisory
  6. 2026-08-10 05:27 UTCVendor advisory
  7. 2026-08-10 01:26 UTCVendor advisory
  8. 2026-08-09 21:25 UTCVendor advisory
  9. 2026-08-09 17:25 UTCEG score recompute
  10. 2026-08-09 17:25 UTCVendor advisory
  11. 2026-08-09 13:46 UTCEPSS rescore
  12. 2026-08-09 13:24 UTCVendor advisory
  13. 2026-08-09 07:06 UTCVendor advisory
  14. 2026-08-08 09:45 UTCVendor advisory
  15. 2026-08-08 05:45 UTCVendor advisory
  16. 2026-08-08 01:44 UTCVendor advisory
  17. 2026-08-07 21:44 UTCVendor advisory
  18. 2026-08-07 17:43 UTCEG score recompute
  19. 2026-08-07 17:43 UTCVendor advisory
  20. 2026-08-06 19:35 UTCEG score recompute
  21. 2026-08-06 19:35 UTCVendor advisory
  22. 2026-08-06 13:46 UTCEPSS rescore
  23. 2026-08-06 10:29 UTCVendor advisory
  24. 2026-08-06 05:45 UTCVendor advisory
  25. 2026-08-06 01:45 UTCEG score recompute
  26. 2026-08-06 01:45 UTCVendor advisory
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 04:56 UTCVendor advisory
  30. 2026-08-04 00:56 UTCVendor advisory
  31. 2026-08-03 01:15 UTCVendor advisory
  32. 2026-08-02 20:54 UTCVendor advisory
  33. 2026-08-02 16:54 UTCEG score recompute
  34. 2026-08-02 16:54 UTCVendor advisory
  35. 2026-08-02 02:26 UTCEPSS rescore
  36. 2026-08-01 04:16 UTCEPSS rescore
  37. 2026-07-30 16:27 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-28 15:36 UTCEPSS rescore
  40. 2026-07-26 14:54 UTCEPSS rescore
  41. 2026-07-26 14:54 UTCEPSS rescore
  42. 2026-07-25 14:18 UTCEPSS rescore
  43. 2026-07-25 14:17 UTCEPSS rescore
  44. 2026-07-24 14:17 UTCEPSS rescore
  45. 2026-07-23 14:18 UTCEPSS rescore
  46. 2026-07-23 14:18 UTCEPSS rescore
  47. 2026-07-23 03:08 UTCEG score recompute 0.50
  48. 2026-07-22 14:08 UTCEPSS rescore
  49. 2026-07-22 14:08 UTCEPSS rescore
  50. 2026-07-21 15:24 UTCEPSS rescore
  51. 2026-07-21 15:24 UTCEPSS rescore
  52. 2026-07-20 17:08 UTCEPSS rescore
  53. 2026-07-20 17:08 UTCEPSS rescore
  54. 2026-07-19 14:31 UTCEPSS rescore
  55. 2026-07-19 14:31 UTCEPSS rescore
  56. 2026-07-19 02:29 UTCEPSS rescore
  57. 2026-07-18 10:04 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-17 07:46 UTCOSV refresh
  60. 2026-07-16 17:03 UTCEPSS rescore
  61. 2026-07-16 17:03 UTCEPSS rescore
  62. 2026-07-15 16:57 UTCEPSS rescore
  63. 2026-07-15 16:57 UTCEPSS rescore
  64. 2026-07-15 02:22 UTCNVD updateCVSS v3 → 9.1 · severity → CRITICAL
  65. 2026-07-15 02:00 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-15 01:21 UTCMITRE cvelistV5CVSS v3 → 8.6 · severity → HIGH
  68. 2026-07-13 22:30 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-09 19:10 UTCEPSS rescore
  74. 2026-07-08 15:15 UTCEPSS rescore
  75. 2026-07-06 16:27 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-28500?
CVE-2026-28500 is a critical vulnerability 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 CVE-2026-28500 disclosed?
CVE-2026-28500 was first published in the National Vulnerability Database on March 16, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-28500 actively exploited?
CVE-2026-28500 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 75.3% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-28500, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.