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
Elevated
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.3%CVSS: 9.1Exploit: Elevated riskExposed 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 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%
EPSS PROB
0.3%
EPSS %ILE
21st
KEV
Not listed

Published

March 16, 2026

Last Modified

July 15, 2026

Advisory Details (6)

Auto-updated Sep 16, 2026
Patch available. Sources: github, redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-28500.json
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-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
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24977
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(3)

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 / EcosystemFix (by version range) / 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 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 5× in last 7d / 24× 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 186 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.3% probability of exploitation in the next 30 days (21st 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.

Book a Demo →Browse All CVEs