NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2024-8676 — cri-o

HIGHFix: cri-o/cri-o@e8e7dcb

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

Also known asGHSA-7p9f-6x8j-gxxpGO-2024-3292
Published
Updated
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs55th percentile — riskier than 55% of all scored CVEsHighest risk
0.00%0.42%0.85%1.27%0.3%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐹github.com/cri-o/cri-o🐹github.com/cri-o/cri-o🐹github.com/cri-o/cri-o

Real-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

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/cri-o/cri-oall versions1.29.11go get github.com/cri-o/cri-o@v1.29.11
🐹Gogithub.com/cri-o/cri-o≥ 1.30.0&&< 1.30.81.30.8go get github.com/cri-o/cri-o@v1.30.8
🐹Gogithub.com/cri-o/cri-o≥ 1.31.0&&< 1.31.31.31.3go get github.com/cri-o/cri-o@v1.31.3

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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.

  3. 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.

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.

Red HatModerate
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for CVE-2024-8676 (CC BY 4.0)
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 4.15cri-o-0:1.28.11-7.rhaos4.15.gitc4c0556.el8RHSA-2025:0648
Red Hat OpenShift Container Platform 4.16cri-o-0:1.29.11-3.rhaos4.16.git16d9bd6.el8RHBA-2024:10826
Red Hat OpenShift Container Platform 4.16openshift/ose-rhel-coreos-9:416.94.202506251808-0RHSA-2025:9765
Red Hat OpenShift Container Platform 4.17openshift/ose-rhel-coreos-9:417.94.202503241418-0RHSA-2025:3297
Red Hat OpenShift Container Platform 4.18cri-o-0:1.31.5-5.rhaos4.18.git6dfa0a6.el8RHSA-2025:1908
Red Hat OpenShift Container Platform 4.18openshift/ose-rhel-coreos-9:418.94.202504231329-0RHSA-2025:4211

Frequently Asked Questions

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 end
O3 Security · Impact-Aware SCA

Is CVE-2024-8676 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2024-8676: cri-o — Fixed in 1.29.11