CVE-2026-24253

HIGHPre-NVD 8.28.2—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.2Exploit: None knownExposed: 0

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

NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to denial of service and data tampering.

CVSS v3
8.2
EG Score
8.2(high)
EG Risk
52(Track)
EG Risk 52/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
Severity82% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
29%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 7, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

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

https://github.com/NVIDIA/product-security/tree/main/2026/5842
generic
https://www.cve.org/CVERecord?id=CVE-2026-24253

Vendor Advisories for CVE-2026-24253(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 28× in last 7d / 68× 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-08-20 22:55 UTCEPSS rescore
  2. 2026-08-20 19:28 UTCGHSA enrichment
  3. 2026-08-20 07:30 UTCGHSA enrichment
  4. 2026-08-19 19:31 UTCEG score recompute
  5. 2026-08-19 19:31 UTCGHSA enrichment
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-19 07:33 UTCGHSA enrichment
  8. 2026-08-18 19:33 UTCEG score recompute
  9. 2026-08-18 19:33 UTCGHSA enrichment
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 07:35 UTCGHSA enrichment
  12. 2026-08-17 19:34 UTCEG score recompute
  13. 2026-08-17 19:34 UTCGHSA enrichment
  14. 2026-08-17 13:47 UTCEPSS rescore
  15. 2026-08-17 07:17 UTCGHSA enrichment
  16. 2026-08-16 19:19 UTCEG score recompute
  17. 2026-08-16 19:19 UTCGHSA enrichment
  18. 2026-08-16 14:56 UTCEPSS rescore
  19. 2026-08-16 07:21 UTCEG score recompute
  20. 2026-08-16 07:21 UTCGHSA enrichment
  21. 2026-08-16 02:14 UTCEPSS rescore
  22. 2026-08-15 19:23 UTCGHSA enrichment
  23. 2026-08-15 07:25 UTCEG score recompute
  24. 2026-08-15 07:25 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 43 more
  1. 2026-08-14 19:26 UTCGHSA enrichment
  2. 2026-08-14 07:28 UTCEG score recompute
  3. 2026-08-14 07:28 UTCGHSA enrichment
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 19:30 UTCGHSA enrichment
  6. 2026-08-13 07:32 UTCGHSA enrichment
  7. 2026-08-12 19:33 UTCEG score recompute
  8. 2026-08-12 19:33 UTCGHSA enrichment
  9. 2026-08-12 13:50 UTCEPSS rescore
  10. 2026-08-12 07:35 UTCGHSA enrichment
  11. 2026-08-11 19:37 UTCEG score recompute
  12. 2026-08-11 19:37 UTCGHSA enrichment
  13. 2026-08-11 13:42 UTCEPSS rescore
  14. 2026-08-11 07:35 UTCEG score recompute
  15. 2026-08-11 07:35 UTCGHSA enrichment
  16. 2026-08-11 00:00 UTCEPSS rescore
  17. 2026-08-10 19:37 UTCGHSA enrichment
  18. 2026-08-10 07:39 UTCGHSA enrichment
  19. 2026-08-09 19:41 UTCEG score recompute
  20. 2026-08-09 19:41 UTCGHSA enrichment
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 07:43 UTCGHSA enrichment
  23. 2026-08-08 19:45 UTCEG score recompute
  24. 2026-08-08 19:45 UTCGHSA enrichment
  25. 2026-08-08 16:37 UTCEPSS rescore
  26. 2026-08-08 07:47 UTCGHSA enrichment
  27. 2026-08-07 19:49 UTCEG score recompute
  28. 2026-08-07 19:49 UTCGHSA enrichment
  29. 2026-08-07 15:46 UTCGHSA enrichment
  30. 2026-08-07 03:48 UTCGHSA enrichment
  31. 2026-08-06 15:50 UTCEG score recompute
  32. 2026-08-06 15:50 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-06 07:20 UTCGHSA enrichment
  35. 2026-08-05 19:22 UTCEG score recompute
  36. 2026-08-05 19:22 UTCGHSA enrichment
  37. 2026-08-05 19:17 UTCEPSS rescore
  38. 2026-08-05 07:24 UTCGHSA enrichment
  39. 2026-08-04 19:25 UTCEG score recompute
  40. 2026-08-04 19:25 UTCGHSA enrichment
  41. 2026-08-04 18:24 UTCEG score recompute
  42. 2026-08-04 17:48 UTCEG score recompute
  43. 2026-08-04 17:46 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24253?
CVE-2026-24253 is a high vulnerability published on August 4, 2026. NVIDIA Dynamo for Linux contains a vulnerability where an attacker could cause an out-of-bounds write. A successful exploit of this vulnerability might lead to denial of service and data tampering.
When was CVE-2026-24253 disclosed?
CVE-2026-24253 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-24253 actively exploited?
CVE-2026-24253 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 71.5% of all scored CVEs.
What is the CVSS score of CVE-2026-24253?
CVE-2026-24253 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-24253?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24253, 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-24253

Explore →

Is Your Infrastructure Affected by CVE-2026-24253?

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

Start Free Scan →Browse All CVEs