Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
A flaw was found in CRIU's handling of restartable sequences (rseq) during checkpoint/restore. A malicious process inside a container can register an rseq critical section that hijacks CRIU's parasite code injection during checkpoint, allowing it to spoof the process credentials saved in the checkpoint image. On restore, the container process gains elevated capabilities and zeroed UIDs/GIDs. The practical impact on Red Hat products is limited by several factors: checkpoint/restore requires root privileges (podman) or cluster-admin RBAC (OpenShift) to trigger and cannot be initiated from within the container itself; on OpenShift prior to 4.17 the feature required explicit opt-in, and on 4.17+ the kubelet checkpoint API RBAC is not configured by default; OpenShift enforces user namespaces by default for regular workloads (hostUsers is gated behind admin-only SCCs), which makes the spoofed capabilities namespace-scoped and ineffective for privilege escalation; SELinux type enforcement (container_t) blocks privilege transitions independently of capabilities; seccomp filters persist through checkpoint/restore and cannot be corrupted via the parasite; and kernel mount namespace ownership checks on RHEL 9/10 kernels prevent mount-based container escape even with spoofed capabilities.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
AVAILABLE
Momentum
NONE
CVE-2026-18107: a container using CRIU checkpoint/restore can hijack the parasite injection, spoof its UID/GID, and wake up with elevated capabilities. Here's what actually stops it (and what doesn't).
Post summary
The text explains how CRIU checkpoint/restore can be abused for privilege escalation in containers and notes that some mitigations exist, but no PoC, exploit, or evidence of active exploitation is mentioned.
Takeaway: defense-in-depth works. SELinux + user namespaces + RBAC turned a container escape into a non-event. If your stack doesn't have all three, treat checkpoint images as untrusted input. Source: https://nvd.nist.gov/vuln/detail/CVE-2026-18107
Post summary
The post explains that CVE‑2026‑18107, a container escape, was mitigated through SELinux, user namespaces, and RBAC, and advises treating checkpoint images as untrusted inputs when those controls are lacking.