CVE-2026-24217

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-20. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

NVIDIA BioNeMo Core for Linux contains a vulnerability where a user could cause a path traversal by loading a malicious file. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.8%
EPSS %ILE
54th
KEV
Not listed

Published

May 20, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated May 22, 2026
No fix on record yet.
generic
https://www.cve.org/CVERecord?id=CVE-2026-24217

Vendor Advisories for CVE-2026-24217(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 22× 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 268 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24217?
CVE-2026-24217 is a high vulnerability published on May 20, 2026. NVIDIA BioNeMo Core for Linux contains a vulnerability where a user could cause a path traversal by loading a malicious file. A successful exploit of this vulnerability might lead to code execution, denial of service, information disclosure, and data tampering.
When was CVE-2026-24217 disclosed?
CVE-2026-24217 was first published on May 20, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24217 actively exploited?
CVE-2026-24217 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24217?
CVE-2026-24217 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-24217?
No fix for CVE-2026-24217 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-24217 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-24217

Explore →

Is Your Infrastructure Affected by CVE-2026-24217?

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

Book a Demo →Browse All CVEs