CVE-2022-0811: cr8escape: CRI-O Arbitrary Sysctl Injection Container Escape
- Vendor
- Kubernetes
CVE-2022-0811, also known as cr8escape, is a code-injection flaw in CRI-O's handling of pod sysctl settings. A user authorized to deploy a pod can supply a crafted sysctl value that causes CRI-O to set arbitrary kernel parameters on the node rather than enforcing the intended restrictions. An attacker can set kernel.core_pattern and use the resulting kernel helper execution behavior to escape the container and execute attacker-controlled code with root privileges on the Kubernetes node hosting the pod.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation yields a container escape and arbitrary code execution as root on the affected Kubernetes node. The attacker gains host-level control of the node where the malicious pod is scheduled, enabling access to host resources, credentials, workloads, and potentially further cluster compromise.
Mitigation
If you can’t patch tonight, do this now.
For CRI-O 1.19 and 1.20, set manage_ns_lifecycle to false so that sysctl configuration is delegated to the OCI runtime, which generally filters the malicious cases. Restrict pod-creation privileges to trusted principals. As compensating controls, use an admission webhook to reject sysctl values containing '+', or enforce a policy that forbids pod sysctls entirely, after assessing workload compatibility.
Remediation
Patch, then assume compromise.
Upgrade CRI-O to a fixed release: 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, 1.24.0, or a later supported release. Apply vendor-provided updates to all Kubernetes nodes using CRI-O and restart or roll nodes as required to ensure the updated runtime is active.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2022-0811 exploited in the wild?
- As of Oct 16, 2026, Mallory has no reports of CVE-2022-0811 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2022-0811?
- As of Oct 16, 2026, Mallory has found no public exploit for CVE-2022-0811.
- Is there a patch for CVE-2022-0811?
- Upgrade CRI-O to a fixed release: 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, 1.24.0, or a later supported release. Apply vendor-provided updates to all Kubernetes nodes using CRI-O and restart or roll nodes as required to ensure the updated runtime is active.
- What products are affected by CVE-2022-0811?
- Kubernetes Cri-O.
- How severe is CVE-2022-0811?
- CVE-2022-0811 has a CVSS v3.1 score of 8.8 (High) and an EPSS score of 19.0% (97th percentile) as of Oct 16, 2026.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.