CVE-2022-0811

published 16 Mar 2022 · updated 18 Feb 2026

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.

9.3CriticalCVSS 8.8EPSS 19%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 19%. No fixed version is recorded.

A flaw was found in CRI-O in the way it set kernel options for a pod. This issue allows anyone with rights to deploy a pod on a Kubernetes cluster that uses the CRI-O runtime to achieve a container escape and arbitrary code execution as root on the cluster node, where the malicious pod was deployed.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
=cri-o 1.24.0, cri-o 1.23.2, cri-o 1.22.3, cri-o 1.21.6, cri-o 1.20.7, cri-o 1.19.6

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-0811 severity on Zeptric[![CVE-2022-0811](https://zeptric.io/badge/cve/CVE-2022-0811.svg)](https://zeptric.io/cve/CVE-2022-0811)