CVE-2026-24243

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
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

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

NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. 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.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 2, 2026
No patch confirmed 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-24243(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 18× in last 7d / 105× 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 188 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-24243?
CVE-2026-24243 is a high vulnerability published on July 1, 2026. NVIDIA Megatron Bridge for Linux contains a vulnerability where an attacker could cause deserialization of untrusted data. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, data tampering, and information disclosure.
When was CVE-2026-24243 disclosed?
CVE-2026-24243 was first published in the National Vulnerability Database 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-24243 actively exploited?
CVE-2026-24243 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 64.2% of all scored CVEs.
What is the CVSS score of CVE-2026-24243?
CVE-2026-24243 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-24243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24243, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-24243?

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