CVE-2024-8676

HIGHNVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.4Exploit: None knownExposed: 0

A fix is available — apply it.

A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the pod spec, verifying that the pod has access to the mounts it specifies are not applicable to a restored container. This flaw allows a malicious user to trick CRI-O into restoring a pod that doesn't have access to host mounts. The user needs access to the kubelet or cri-o socket to call the restore endpoint and trigger the restore.

CVSS v3
7.4
EG Score
7.4(medium)
EG Risk
34(Track)
EG Risk 34/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
Severity74% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
54%
KEV
Not listed

Published

November 26, 2024

Last Modified

August 21, 2026

Advisory Details (8)

Auto-updated Aug 21, 2026
Patch available. Sources: redhat.
redhat Patch Available

2313842 – (CVE-2024-8676) CVE-2024-8676 cri-o: Checkpoint restore can be triggered from different namespaces

https://bugzilla.redhat.com/show_bug.cgi?id=2313842
redhat Patch Available

CVE-2024-8676 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2024-8676
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:9765
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:4211
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:3297
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:1908
redhat Patch Available
https://access.redhat.com/errata/RHSA-2025:0648
redhat Patch Available
https://access.redhat.com/errata/RHBA-2024:10826

Vendor Advisories for CVE-2024-8676(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhcos-416.94.202506251808-02025-07-02redhat
redhatrhcos-418.94.202504231329-02025-05-01redhat
redhatrhcos-417.94.202503241418-02025-04-03redhat
redhatcri-o-0:1.31.5-5.rhaos4.18.git6dfa0a6.el82025-03-04redhat
redhatcri-o-0:1.28.11-7.rhaos4.15.gitc4c0556.el82025-01-29redhat
redhatcri-o-0:1.29.11-3.rhaos4.16.git16d9bd6.el82024-12-12redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/cri-o/cri-o—1.31.3—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 32× 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 180 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-8676?
CVE-2024-8676 is a high vulnerability published on November 26, 2024. A vulnerability was found in CRI-O, where it can be requested to take a checkpoint archive of a container and later be asked to restore it. When it does that restoration, it attempts to restore the mounts from the restore archive instead of the pod request. As a result, the validations run on the…
When was CVE-2024-8676 disclosed?
CVE-2024-8676 was first published in the National Vulnerability Database on November 26, 2024, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-8676 actively exploited?
CVE-2024-8676 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.4% of all scored CVEs.
What is the CVSS score of CVE-2024-8676?
CVE-2024-8676 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2024-8676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-8676, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-8676

Explore →

Is Your Infrastructure Affected by CVE-2024-8676?

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

Start Free Scan →Browse All CVEs