Advisory record · GHSA-6x2m-w449-qwx7

Code Injection in CRI-O

CVSS 8.8 HighCriticalEPSS 0.19 · 97th percentile

Critical, because:

  • CVSS score 8.8 (7.0 or more) and EPSS 0.19 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Mar 2022, 20:13 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/cri-o/cri-oGo>=1.19.0, <1.19.6 || >=1.20.0, <1.20.7 || >=1.21.0, <1.21.6 || >=1.22.0, <1.22.3 || >=1.23.0, <1.23.21.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2
Identifiers
GHSA-6x2m-w449-qwx7 · CVE-2022-0811 · GO-2022-0354
Weakness (CWE)
CWE-94
Published
15 Mar 2022
Updated
8 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

CRI-O versions 1.19.0 through before 1.19.6, 1.20.0 through before 1.20.7, 1.21.0 through before 1.21.6, 1.22.0 through before 1.22.3, and 1.23.0 through before 1.23.2 can let a user who can deploy pods set arbitrary kernel parameters on the host. An attacker can abuse the kernel.core_pattern parameter to escape the container and run code as root on any node. Upgrade to 1.19.6, 1.20.7, 1.21.6, 1.22.3, 1.23.2, or 1.24.0 or later.

Written 6 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.19, the 97th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.