CVE-2026-24246

HIGHPre-NVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-01. a secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.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 Megatron Bridge for Linux contains a vulnerability where an attacker could cause improper control of dynamically managed code resources. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, and information disclosure.

CVSS v3
7.8
EG Score
7.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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
No fix on record yet.
generic

product-security/2026/5841 at main · NVIDIA/product-security · GitHub

https://github.com/NVIDIA/product-security/tree/main/2026/5841

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

Frequently asked(5)

What is CVE-2026-24246?
CVE-2026-24246 is a high vulnerability published on July 1, 2026. NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause improper control of dynamically managed code resources. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, and information disclosure.
When was CVE-2026-24246 disclosed?
CVE-2026-24246 was first published on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24246 actively exploited?
CVE-2026-24246 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-24246?
CVE-2026-24246 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-24246?
No fix for CVE-2026-24246 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-24246 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24246?

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