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.
CVE-2026-24251
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.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(high)
- EPSS
- 5.1%
- KEV
- Not listed
Published
July 1, 2026
Last Modified
July 2, 2026
Advisory Details (2)
Auto-updated Jul 2, 2026product-security/2026/5841 at main · NVIDIA/product-security · GitHub
https://github.com/NVIDIA/product-security/tree/main/2026/5841Vendor Advisories for CVE-2026-24251(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 31× in last 7d / 31× 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.
- 2026-07-07 03:07 UTCEG score recompute
- 2026-07-07 03:07 UTCGHSA enrichment
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 16:27 UTCEPSS rescore
- 2026-07-06 15:18 UTCEG score recompute
- 2026-07-06 15:18 UTCGHSA enrichment
- 2026-07-06 03:29 UTCEG score recompute
- 2026-07-06 03:29 UTCGHSA enrichment
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-06 02:23 UTCEPSS rescore
- 2026-07-05 15:33 UTCEG score recompute
- 2026-07-05 15:33 UTCGHSA enrichment
- 2026-07-05 03:45 UTCEG score recompute
- 2026-07-05 03:44 UTCGHSA enrichment
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 15:55 UTCEG score recompute
- 2026-07-04 15:55 UTCGHSA enrichment
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-04 04:08 UTCEG score recompute
- 2026-07-04 04:08 UTCGHSA enrichment
- 2026-07-03 16:20 UTCEG score recompute
- 2026-07-03 16:20 UTCGHSA enrichment
- 2026-07-03 04:32 UTCEG score recompute
- 2026-07-03 04:31 UTCGHSA enrichment
Show 6 moreShow fewer
- 2026-07-02 16:43 UTCEG score recompute
- 2026-07-02 16:43 UTCGHSA enrichment
- 2026-07-02 04:55 UTCEG score recompute
- 2026-07-02 04:55 UTCGHSA enrichment
- 2026-07-01 17:08 UTCEG score recompute
- 2026-07-01 17:06 UTCNVD updatefirst tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-502
- CVE-2017-20208EG 9.8CRITICAL
- CVE-2017-20207EG 9.8CRITICAL
- CVE-2017-20206EG 9.8CRITICAL
- CVE-2017-20189EG 9.8CRITICAL
- CVE-2017-10992EG 9.8EPSS 95%CRITICAL
- CVE-2013-4521EG 9.8EPSS 90%CRITICAL
- CVE-2014-1860EG 9.8CRITICAL
- CVE-2016-1000027EG 9.8EPSS 98%CRITICAL
- CVE-2014-3699EG 9.8CRITICAL
- CVE-2017-18605EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-24251?
When was CVE-2026-24251 disclosed?
Is CVE-2026-24251 actively exploited?
What is the CVSS score of CVE-2026-24251?
How do I remediate CVE-2026-24251?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-24251
Is Your Infrastructure Affected by CVE-2026-24251?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.