CVE-2026-24260

HIGHPre-NVD 8.58.5—
EchelonGraph scoreHIGH confidence

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

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

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

NVIDIA Container Toolkit for Linux contains a vulnerability where an attacker could cause a time-of-check time-of-use race condition. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, and data tampering.

CVSS v3
8.5
EG Score
8.5(high)
EG Risk
43(Track)
EG Risk 43/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
Severity85% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
39.2%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 1, 2026
No patch confirmed yet.
generic
https://www.cve.org/CVERecord?id=CVE-2026-24260
generic

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

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

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-24260?
CVE-2026-24260 is a high vulnerability published on July 1, 2026. NVIDIA Container Toolkit for Linux contains a vulnerability where an attacker could cause a time-of-check time-of-use race condition. A successful exploit of this vulnerability might lead to code execution, escalation of privileges, and data tampering.
When was CVE-2026-24260 disclosed?
CVE-2026-24260 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-24260 actively exploited?
CVE-2026-24260 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-24260?
CVE-2026-24260 has a CVSS v3 base score of 8.5 (NVD).
How do I remediate CVE-2026-24260?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-24260, 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-24260

Explore →

Is Your Infrastructure Affected by CVE-2026-24260?

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

Start Free Scan →Browse All CVEs