CVE-2024-8676 Cri-o: checkpoint restore can be triggered from different namespaces

High 7.4 Published 26 Nov 2024 Updated 13 Oct 2026

A malicious user with socket access can bypass mount validations to restore containers with unauthorized host mount access, leading to privilege escalation.

Exploited in the wild: Not known
Login needed: Not needed
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

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

Which versions are affected by CVE-2024-8676?

7 open source packages ship an affected version, including github.com/cri-o/cri-o.

Package	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`

1 more packages

github.com/cri-o/cri-o Go From 1.31.0 1.31.3

Linux distribution packages (12)

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

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2024-8676 being exploited?

There is no known exploitation of CVE-2024-8676 in the wild and no public exploit code.

Sources

Also known as AZL-53540, GHSA-7p9f-6x8j-gxxp, GO-2024-3292, RHBA-2024:10826, RHSA-2025:0648.