# CVE-2024-8676: Cri-o: checkpoint restore can be triggered from different namespaces > A malicious user with socket access can bypass mount validations to restore containers with unauthorized host mount access, leading to privilege escalation. - **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Nov 2024 - **Updated:** 13 Oct 2026 - **Also known as:** AZL-53540, GHSA-7p9f-6x8j-gxxp, GO-2024-3292, RHBA-2024:10826, RHSA-2025:0648 ## What is CVE-2024-8676? CVE-2024-8676 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 8, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2024-8676? 7 open source packages ship an affected version, including github.com/cri-o/cri-o. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/cri-o/cri-o` | Go | All versions | 1.29.11, 1.30.8, 1.31.3 | | `github.com/cri-o/cri-o` | Go | All versions | 1.29.11 | | `github.com/cri-o/cri-o` | Go | All versions | 1.29.11 | | `github.com/cri-o/cri-o` | Go | From 1.30.0 | 1.30.8 | | `github.com/cri-o/cri-o` | Go | From 1.30.0 | 1.30.8 | | `github.com/cri-o/cri-o` | Go | From 1.31.0 | 1.31.3 | | `github.com/cri-o/cri-o` | Go | From 1.31.0 | 1.31.3 | | `cri-o` | Red Hat:openshift:4.15::el8 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.15::el8 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.15::el8 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el8 | | `cri-o` | Red Hat:openshift:4.15::el9 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el9 | | `cri-o-debuginfo` | Red Hat:openshift:4.15::el9 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el9 | | `cri-o-debugsource` | Red Hat:openshift:4.15::el9 | All versions | 0:1.28.11-7.rhaos4.15.gitc4c0556.el9 | | `cri-o` | Red Hat:openshift:4.16::el8 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el8 | | `cri-o-debuginfo` | Red Hat:openshift:4.16::el8 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el8 | | `cri-o-debugsource` | Red Hat:openshift:4.16::el8 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el8 | | `cri-o` | Red Hat:openshift:4.16::el9 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el9 | | `cri-o-debuginfo` | Red Hat:openshift:4.16::el9 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el9 | | `cri-o-debugsource` | Red Hat:openshift:4.16::el9 | All versions | 0:1.29.11-3.rhaos4.16.git16d9bd6.el9 | ## How do I fix CVE-2024-8676? Upgrade github.com/cri-o/cri-o to a fixed version for your release line: 1.29.11, 1.30.8 or 1.31.3. ## Is CVE-2024-8676 being exploited? There is no known exploitation of CVE-2024-8676 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-8676 and fix it if it is affected. What it is: CVE-2024-8676 is a high-severity missing authorization vulnerability in Red Hat Enterprise Linux 8, published on 26 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-8676 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/cri-o/cri-o (Go): affected all versions; fixed in 1.29.11, 1.30.8, 1.31.3 - github.com/cri-o/cri-o (Go): affected all versions; fixed in 1.29.11 - github.com/cri-o/cri-o (Go): affected all versions; fixed in 1.29.11 - github.com/cri-o/cri-o (Go): affected from 1.30.0; fixed in 1.30.8 - github.com/cri-o/cri-o (Go): affected from 1.30.0; fixed in 1.30.8 - github.com/cri-o/cri-o (Go): affected from 1.31.0; fixed in 1.31.3 - github.com/cri-o/cri-o (Go): affected from 1.31.0; fixed in 1.31.3 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-8676/ (Markdown: https://insights.sbomify.com/CVE-2024-8676/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8676 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8676 - OSV: https://osv.dev/vulnerability/CVE-2024-8676 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-8676/ Summaries are generated and may contain mistakes; the official description above is the record.