CVE-2022-0811

Name: CVE-2022-0811
Creator: NVD / NIST
Published: 2022-03-16T15:15:16.123+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

HIGHCVSS 8.8/10EPSS 18.56%

Last modified Jun 17, 2026

CVE-2022-0811 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. 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.. EPSS estimates a 18.56% chance of exploitation in the next 30 days.

Description

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.

Metrics

CVSS 3.1

8.8/10

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

18.56%

96.9th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Kubernetes	Cri-O	>= 1.19.0, < 1.19.6
Kubernetes	Cri-O	>= 1.20.0, < 1.20.7
Kubernetes	Cri-O	>= 1.21.0, < 1.21.6
Kubernetes	Cri-O	>= 1.22.0, < 1.22.3
Kubernetes	Cri-O	>= 1.23.0, < 1.23.2

References

https://bugzilla.redhat.com/show_bug.cgi?id=2059475Issue Tracking, Third Party Advisory
https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7Third Party Advisory
https://bugzilla.redhat.com/show_bug.cgi?id=2059475Issue Tracking, Third Party Advisory
https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7Third Party Advisory

Timeline

Published: Mar 16, 2022
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2022-0811?

How severe is CVE-2022-0811?

CVE-2022-0811 has a CVSS score of 8.8/10 (HIGH severity). The EPSS model estimates a 18.56% probability of exploitation in the next 30 days.

How do I fix CVE-2022-0811?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2022-0811?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST