CVE-2026-24247

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH 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(high)
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
7%
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
https://www.cve.org/CVERecord?id=CVE-2026-24247
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-24247(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 14× 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.

  1. 2026-07-27 01:10 UTCEG score recompute
  2. 2026-07-27 01:10 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 13:17 UTCEG score recompute
  6. 2026-07-26 13:17 UTCGHSA enrichment
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:07 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:31 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-17 02:20 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-16 14:27 UTCGHSA enrichment
  23. 2026-07-16 02:34 UTCGHSA enrichment
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 16:57 UTCEPSS rescore
Show 47 more
  1. 2026-07-15 14:39 UTCGHSA enrichment
  2. 2026-07-15 02:44 UTCGHSA enrichment
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-14 14:44 UTCGHSA enrichment
  6. 2026-07-14 02:49 UTCGHSA enrichment
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 14:57 UTCGHSA enrichment
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 06:13 UTCEPSS rescore
  11. 2026-07-13 03:04 UTCGHSA enrichment
  12. 2026-07-12 15:10 UTCGHSA enrichment
  13. 2026-07-12 05:46 UTCEPSS rescore
  14. 2026-07-12 05:46 UTCEPSS rescore
  15. 2026-07-12 03:15 UTCGHSA enrichment
  16. 2026-07-11 15:22 UTCGHSA enrichment
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-11 03:29 UTCGHSA enrichment
  19. 2026-07-10 15:35 UTCGHSA enrichment
  20. 2026-07-10 03:35 UTCGHSA enrichment
  21. 2026-07-09 19:10 UTCEPSS rescore
  22. 2026-07-09 15:40 UTCGHSA enrichment
  23. 2026-07-09 03:44 UTCGHSA enrichment
  24. 2026-07-08 15:51 UTCGHSA enrichment
  25. 2026-07-08 15:15 UTCEPSS rescore
  26. 2026-07-08 15:15 UTCEPSS rescore
  27. 2026-07-08 03:58 UTCGHSA enrichment
  28. 2026-07-07 16:05 UTCGHSA enrichment
  29. 2026-07-07 13:46 UTCEPSS rescore
  30. 2026-07-07 04:11 UTCGHSA enrichment
  31. 2026-07-06 16:27 UTCEPSS rescore
  32. 2026-07-06 16:27 UTCEPSS rescore
  33. 2026-07-06 16:15 UTCGHSA enrichment
  34. 2026-07-06 04:21 UTCGHSA enrichment
  35. 2026-07-05 16:25 UTCGHSA enrichment
  36. 2026-07-05 04:29 UTCGHSA enrichment
  37. 2026-07-05 02:30 UTCEPSS rescore
  38. 2026-07-04 16:36 UTCGHSA enrichment
  39. 2026-07-04 06:31 UTCEPSS rescore
  40. 2026-07-04 06:31 UTCEPSS rescore
  41. 2026-07-04 04:41 UTCGHSA enrichment
  42. 2026-07-03 16:48 UTCGHSA enrichment
  43. 2026-07-03 04:52 UTCGHSA enrichment
  44. 2026-07-02 16:55 UTCGHSA enrichment
  45. 2026-07-02 05:01 UTCGHSA enrichment
  46. 2026-07-01 17:08 UTCEG score recompute
  47. 2026-07-01 17:06 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24247?
CVE-2026-24247 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-24247 disclosed?
CVE-2026-24247 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-24247 actively exploited?
CVE-2026-24247 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 93.5% of all scored CVEs.
What is the CVSS score of CVE-2026-24247?
CVE-2026-24247 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-24247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24247, 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-24247

Explore →

Is Your Infrastructure Affected by CVE-2026-24247?

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

Start Free Scan →Browse All CVEs