CVE-2022-0811

What it is

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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of data exposure, data tampering, service disruption.

Exploit odds

19.0% chance of exploitation in the next 30 days (EPSS). Higher than most.

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-03-16 15:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 04:21 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 19.0% in the next 30 days (EPSS).
• Severity: 8.8 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-03-16 15:15 UTC

Last modified

2026-06-17 04:21 UTC

Exploit probability

19.0% · EPSS, next 30 days

Weakness

CWE-94 · Code injection

Record status

Modified

Affected

• Kubernetes cri-o < 1.19.6
• Kubernetes cri-o < 1.20.7
• Kubernetes cri-o < 1.21.6
• Kubernetes cri-o < 1.22.3
• Kubernetes cri-o < 1.23.2

Attack profile CVSS 3.1 · 8.8

Attack vector

Network

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-0811.md and follow it. Check whether this project is affected by CVE-2022-0811. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge