Most recent entries from all

EUVD-2026-357274

2026-10-04T12:09:59.597914+00:00

EUVD-2026-357274

fkie_cve-2024-8676

2026-10-04T12:09:59.597973+00:00

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.

GHSA-7p9f-6x8j-gxxp — CRI-O: Maliciously structured checkpoint file can gain arbitrary node access

2026-10-04T12:09:59.598013+00:00

Affected: Go: github.com/cri-o/cri-o

### Impact

### Patches 1.31.1, 1.30.6, 1.29.8

### Workarounds set `enable_criu_support = false`

### References _Are there any links users can visit to find out more?_

openSUSE-SU-2024:14567-1 — govulncheck-vulndb-0.0.20241209T183251-1.1 on GA media

2026-10-04T12:09:59.598044+00:00

govulncheck-vulndb-0.0.20241209T183251-1.1 on GA media

RHBA-2024:10826 — Red Hat Bug Fix Advisory: OpenShift Container Platform 4.16.26 packages and security update

2026-10-04T12:09:59.598075+00:00

cri-o: Checkpoint restore can be triggered from different namespaces

WID-SEC-W-2025-0216 — Red Hat OpenShift Container Platform: Schwachstelle ermöglicht Umgehung von Sicherheitsvorkehrungen

2026-10-04T12:09:59.598092+00:00

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Red Hat OpenShift Container Platform ausnutzen, um Sicherheitsvorkehrungen zu umgehen.