Skip to main content
Public proof of conceptFix available

CVE-2022-0811

A public proof of concept exists; no exploitation attested.

  • Published2022-03-16
  • Fixed in1.23.2 · 1.22.3 · 1.21.6 · 1.20.7 · 1.19.6
  • WeaknessCWE-94

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2022-03-1615:15CVE publishedNVD
  2. 2026-10-2319:23First public proof of conceptPoC-in-GitHub
  3. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-0811?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-0811?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Kubernetes cri-o
BranchAffectedFixed in
1.23≥ 1.23.0, < 1.23.21.23.2
1.22≥ 1.22.0, < 1.22.31.22.3
1.21≥ 1.21.0, < 1.21.61.21.6
1.20≥ 1.20.0, < 1.20.71.20.7
1.19≥ 1.19.0, < 1.19.61.19.6

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Kubernetes cri-o to 1.23.2 · 1.22.3 · 1.21.6 · 1.20.7 · 1.19.6

Detection

read 2026-10-23 19:23 UTC
Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedspiarh/webhook-cve-2022-0811
PoC-in-GitHub

Sources

  • NVDCVSS 3.18.8read 2026-10-23
  • NVDCVSS 2.09read 2026-10-23
  • CNAweakness (CWE)CWE-94read 2026-10-23
  • NVDweakness (CWE)CWE-94read 2026-10-23
  • FIRST EPSSEPSS score19.0 %read 2026-10-23
  • PoC-in-GitHubproof of concept1read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Published
2022-03-16
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2022-0811?

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.

Is CVE-2022-0811 actively exploited?

Active exploitation of CVE-2022-0811 has not been confirmed. Its EPSS score was 19.0% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2022-0811?

CVE-2022-0811 has a CVSS v3 base score of 8.8 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database