CVE-2022-0811

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 18.6%, top 3% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 19%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
60(Track)
EG Risk 60/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
19%
EPSS %ILE
97%
KEV
Not listed

Published

March 16, 2022

Last Modified

November 21, 2024

Advisory Details (2)

Auto-updated Jul 30, 2026
Patch available. Sources: redhat, github.
github Patch Available

cri-o: Arbitrary code execution in cri-o via abusing “kernel.core_pattern” kernel parameter · Advisory · cri-o/cri-o · GitHub

https://github.com/cri-o/cri-o/security/advisories/GHSA-6x2m-w449-qwx7
redhat Patch Available

2059475 – (CVE-2022-0811) CVE-2022-0811 CRI-O: Arbitrary code execution in cri-o via abusing “kernel.core_pattern” kernel parameter

https://bugzilla.redhat.com/show_bug.cgi?id=2059475

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcri-o-0:1.19.5-3.rhaos4.6.git91f8458.el72022-03-23redhat
redhatcri-o-0:1.20.6-11.rhaos4.7.git76ea3d0.el72022-03-22redhat
redhatcri-o-0:1.21.5-3.rhaos4.8.gitaf64931.el72022-03-22redhat
redhatcri-o-0:1.22.2-3.rhaos4.9.gitb030be8.el72022-03-21redhat
redhatcri-o-0:1.23.1-12.rhaos4.10.git1607c6e.el72022-03-15redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/cri-o/cri-o—1.23.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(6)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 145 total refreshes for this CVE.

  1. 2026-09-25 02:54 UTCOSV refresh
  2. 2026-09-24 14:00 UTCEPSS rescore
  3. 2026-09-24 14:00 UTCEPSS rescore
  4. 2026-09-23 13:45 UTCEPSS rescore
  5. 2026-09-22 14:44 UTCEPSS rescore
  6. 2026-09-21 20:28 UTCEPSS rescore
  7. 2026-09-19 15:38 UTCEPSS rescore
  8. 2026-09-18 19:24 UTCEPSS rescore
  9. 2026-09-17 19:23 UTCEPSS rescore
  10. 2026-09-16 14:05 UTCEPSS rescore
  11. 2026-09-16 14:05 UTCEPSS rescore
  12. 2026-09-15 03:06 UTCEPSS rescore
  13. 2026-09-12 14:57 UTCEPSS rescore
  14. 2026-09-11 14:49 UTCEPSS rescore
  15. 2026-09-11 09:33 UTCEPSS rescore
  16. 2026-09-08 21:57 UTCEPSS rescore
  17. 2026-09-06 13:45 UTCEPSS rescore
  18. 2026-09-05 18:51 UTCOSV refresh
  19. 2026-09-05 15:25 UTCEPSS rescore
  20. 2026-09-04 13:57 UTCEPSS rescore
  21. 2026-09-04 05:03 UTCEPSS rescore
  22. 2026-09-02 14:09 UTCEPSS rescore
  23. 2026-09-01 13:51 UTCEPSS rescore
  24. 2026-08-30 19:14 UTCEPSS rescore
  25. 2026-08-30 01:19 UTCEPSS rescore
Show 75 more
  1. 2026-08-28 21:38 UTCEPSS rescore
  2. 2026-08-27 14:22 UTCEPSS rescore
  3. 2026-08-26 14:43 UTCEPSS rescore
  4. 2026-08-25 13:46 UTCEPSS rescore
  5. 2026-08-24 14:13 UTCEPSS rescore
  6. 2026-08-21 23:46 UTCEPSS rescore
  7. 2026-08-20 22:52 UTCEPSS rescore
  8. 2026-08-19 17:01 UTCEPSS rescore
  9. 2026-08-19 05:29 UTCOSV refresh
  10. 2026-08-18 13:45 UTCEPSS rescore
  11. 2026-08-17 13:44 UTCEPSS rescore
  12. 2026-08-16 14:53 UTCEPSS rescore
  13. 2026-08-16 02:11 UTCEPSS rescore
  14. 2026-08-15 01:27 UTCEPSS rescore
  15. 2026-08-13 21:57 UTCEPSS rescore
  16. 2026-08-12 13:48 UTCEPSS rescore
  17. 2026-08-11 13:38 UTCEPSS rescore
  18. 2026-08-09 13:44 UTCEPSS rescore
  19. 2026-08-08 16:34 UTCEPSS rescore
  20. 2026-08-07 16:24 UTCEPSS rescore
  21. 2026-08-06 13:44 UTCEPSS rescore
  22. 2026-08-05 19:15 UTCEPSS rescore
  23. 2026-08-04 15:06 UTCEPSS rescore
  24. 2026-08-04 10:34 UTCEPSS rescore
  25. 2026-08-04 00:57 UTCOSV refresh
  26. 2026-08-03 10:33 UTCEPSS rescore
  27. 2026-08-01 04:13 UTCEPSS rescore
  28. 2026-07-30 16:25 UTCEPSS rescore
  29. 2026-07-28 15:33 UTCEPSS rescore
  30. 2026-07-26 14:52 UTCEPSS rescore
  31. 2026-07-25 14:15 UTCEPSS rescore
  32. 2026-07-24 14:15 UTCEPSS rescore
  33. 2026-07-24 14:15 UTCEPSS rescore
  34. 2026-07-23 14:16 UTCEPSS rescore
  35. 2026-07-23 02:07 UTCEG score recompute
  36. 2026-07-22 22:53 UTCEG score recompute
  37. 2026-07-22 14:06 UTCEPSS rescore
  38. 2026-07-21 15:22 UTCEPSS rescore
  39. 2026-07-21 15:22 UTCEPSS rescore
  40. 2026-07-20 17:05 UTCEPSS rescore
  41. 2026-07-19 02:27 UTCEPSS rescore
  42. 2026-07-19 02:27 UTCEPSS rescore
  43. 2026-07-18 10:02 UTCEPSS rescore
  44. 2026-07-17 19:59 UTCOSV refresh
  45. 2026-07-16 17:00 UTCEPSS rescore
  46. 2026-07-16 17:00 UTCEPSS rescore
  47. 2026-07-15 16:55 UTCEPSS rescore
  48. 2026-07-15 01:58 UTCEPSS rescore
  49. 2026-07-15 01:58 UTCEPSS rescore
  50. 2026-07-13 22:27 UTCEPSS rescore
  51. 2026-07-12 05:44 UTCEPSS rescore
  52. 2026-07-11 08:25 UTCEPSS rescore
  53. 2026-07-09 19:07 UTCEPSS rescore
  54. 2026-07-09 19:07 UTCEPSS rescore
  55. 2026-07-08 15:12 UTCEPSS rescore
  56. 2026-07-08 15:12 UTCEPSS rescore
  57. 2026-07-07 13:43 UTCEPSS rescore
  58. 2026-07-06 16:25 UTCEPSS rescore
  59. 2026-07-06 16:25 UTCEPSS rescore
  60. 2026-07-05 02:28 UTCEPSS rescore
  61. 2026-07-05 02:28 UTCEPSS rescore
  62. 2026-07-04 06:29 UTCEPSS rescore
  63. 2026-07-04 06:29 UTCEPSS rescore
  64. 2026-07-01 15:04 UTCEPSS rescore
  65. 2026-06-30 23:20 UTCEPSS rescore
  66. 2026-06-29 17:53 UTCOSV refresh
  67. 2026-06-28 14:05 UTCEPSS rescore
  68. 2026-06-28 04:54 UTCEPSS rescore
  69. 2026-06-28 04:54 UTCEPSS rescore
  70. 2026-06-27 03:07 UTCEPSS rescore
  71. 2026-06-27 03:06 UTCEPSS rescore
  72. 2026-06-25 13:48 UTCEPSS rescore
  73. 2026-06-25 13:48 UTCEPSS rescore
  74. 2026-06-24 14:03 UTCEPSS rescore
  75. 2026-06-24 14:03 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCspiarh/webhook-cve-2022-0811
    First seen Mar 21, 2022

    Simple webhook to block exploitation of CVE-2022-0811

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-0811?
CVE-2022-0811 is a high vulnerability published on March 16, 2022. 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.
When was CVE-2022-0811 disclosed?
CVE-2022-0811 was first published in the National Vulnerability Database on March 16, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-0811 actively exploited?
CVE-2022-0811 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19% probability of exploitation in the next 30 days, which ranks it in the top 2.8% of all scored CVEs.
What is the CVSS score of CVE-2022-0811?
CVE-2022-0811 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2022-0811?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-0811, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-0811

Explore →

Is Your Infrastructure Affected by CVE-2022-0811?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs