RATATOSK
← All releases

CRI-Ov1.34.12

Security 3Important fixes 1

Get CRI-O alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security3critical1high1medium1

CRI-O sandbox state poisoning fixed

critical
AffectsNot stated in the release notes
Additional actionAll running containers on the nodes wiped during the CRI-O upgrade

An attacker who could create a Pod with arbitrary annotations could poison persisted sandbox state. After a CRI-O restart or node reboot, containers recreated in the affected sandbox could mount attacker-controlled host paths, potentially exposing the CRI-O socket and enabling container escape.

Show release-note lines
Security advisory
A user who can create a Pod with arbitrary annotations can poison persisted CRI-O sandbox state. After a CRI-O restart or node reboot, containers recreated in the affected sandbox may mount attacker-controlled host paths, potentially exposing the CRI-O socket and enabling container escape.
The users must wipe all running containers on the nodes when upgrading CRI-O
Admission webhook rejecting Pod annotations and labels with the io.kubernetes.cri-o. prefix. For example, a validating webhook that denies any Pod whose metadata.annotations or metadata.labels contain keys starting with io.kubernetes.cri-o.
github.com/cri-o/cri-o/security/advisories/GHSA-6wmc-5877-hgc9
Security advisory
CRI-O sandbox state poisoning after restart can expose crio.sock
github.com/cri-o/cri-o/security/advisories/GHSA-6wmc-5877-hgc9

CRI-O HOME newline injection bypass fixed

high
Affectscontainer HOME environment variables

When an attacker able to set a container's environment put an actual newline in HOME, the check matched only the literal characters \n, allowing arbitrary lines to be added to /etc/passwd. CRI-O now rejects HOME values containing actual newline or carriage-return bytes with an error; values without those bytes are not rejected by this check.

Show release-note lines
#### Uncategorized
 - Fixed CVE-2026-15809: bypass of CVE-2022-4318 fix allowing /etc/passwd injection via newline characters in the HOME environment variable. The original check incorrectly matched the literal string "\n" instead of actual newline bytes. (#10217, @aksjadha)
github.com/cri-o/cri-o/releases/tag/v1.34.12

CRI-O daemon crash from malformed OCI image entries fixed

medium
AffectsNot stated in the release notes

A crafted OCI image with an environment entry missing = could crash the daemon when the container spec had no environment variables. This release prevents that crash.

Show release-note lines
Security advisory
A crafted OCI image with a malformed environment variable entry can crash the CRI-O daemon.
This only occurs when no environment variables are set in the container spec. In standard Kubernetes deployments, the kubelet always injects default environment variables, so this issue is not triggered through the normal Kubernetes API path. Environments where containers are created without default environment variables, such as direct CRI API callers, may be affected.
- Use a standard Kubernetes setup where the kubelet manages container lifecycle. The kubelet always injects default environment variables, which prevents this issue from being triggered.
- Restrict container images to trusted registries using admission controllers (e.g. Kyverno, OPA/Gatekeeper).
- Validate OCI image configurations before publishing, rejecting any image whose config.Env contains entries without a = delimiter.
github.com/cri-o/cri-o/security/advisories/GHSA-v5pw-cc82-qrf6
Security advisory
Denial of Service (DoS) — CRI-O daemon crash via crafted OCI image.
github.com/cri-o/cri-o/security/advisories/GHSA-v5pw-cc82-qrf6

Important fixes1

  • User namespace mappings restored at CRI-O startup
    Affectscontainers using user namespaces with ID-mapped mounts

    Before this fix, these containers could fail with “permission denied” after a CRI-O restart or when the real container process was killed with kill 1, because their namespace mappings were not loaded. The restored mappings prevent these failures.

     - User namespace UID/GID mappings are now correctly restored after CRI-O restart, fixing "permission denied" errors for containers using user namespaces with ID-mapped mounts. (#10231, @Chandan9112)
    github.com/cri-o/cri-o/releases/tag/v1.34.12

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.