CVE-2024-8676 is a high-severity (CVSS 7.4) CWE-285 vulnerability in github.com/cri-o/cri-o. A fix is available for github.com/cri-o/cri-o — see the affected versions and patch details below.
Cri-o: checkpoint restore can be triggered from different namespaces
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-8676.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2024-8676 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/cri-o/cri-o🐹github.com/cri-o/cri-o🐹github.com/cri-o/cri-oReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/cri-o/cri-o | all versions | 1.29.11go get github.com/cri-o/cri-o@v1.29.11 |
| 🐹Go | github.com/cri-o/cri-o | ≥ 1.30.0&&< 1.30.8 | 1.30.8go get github.com/cri-o/cri-o@v1.30.8 |
| 🐹Go | github.com/cri-o/cri-o | ≥ 1.31.0&&< 1.31.3 | 1.31.3go get github.com/cri-o/cri-o@v1.31.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/cri-o/cri-o, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/cri-o/cri-o to 1.29.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-8676 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-8676 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-8676. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 4.15 | cri-o-0:1.28.11-7.rhaos4.15.gitc4c0556.el8 | RHSA-2025:0648 |
| Red Hat OpenShift Container Platform 4.16 | cri-o-0:1.29.11-3.rhaos4.16.git16d9bd6.el8 | RHBA-2024:10826 |
| Red Hat OpenShift Container Platform 4.16 | rhcos-416.94.202506251808-0 | RHSA-2025:9765 |
| Red Hat OpenShift Container Platform 4.17 | rhcos-417.94.202503241418-0 | RHSA-2025:3297 |
| Red Hat OpenShift Container Platform 4.18 | cri-o-0:1.31.5-5.rhaos4.18.git6dfa0a6.el8 | RHSA-2025:1908 |
| Red Hat OpenShift Container Platform 4.18 | rhcos-418.94.202504231329-0 | RHSA-2025:4211 |
Frequently Asked Questions
Is CVE-2024-8676 in your dependencies?
O3 Security finds CVE-2024-8676 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.