Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
CRI-O versions before 1.22.5, from 1.23.0 before 1.23.3, and from 1.24.0 before 1.24.1 are vulnerable. An attacker who can run ExecSync commands in a container, such as through a pod using a trusted or untrusted image, can produce very large command output that exhausts memory or disk on the node and denies service to other workloads. Upgrade to CRI-O 1.22.5, 1.23.3, 1.24.1 or later. The source lists no workaround beyond using only trusted images.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS 0.032, the 88th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:05 UTC First seen by agentprime
- 31 Oct 2026, 15:05 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-fcm2-6c3h-pg6j
- OSV: GHSA-fcm2-6c3h-pg6j
- github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j
- nvd.nist.gov/vuln/detail/CVE-2022-1708
- github.com/cri-o/cri-o/commit/f032cf649ecc7e0c46718bd9e7814bfb317cb544
- bugzilla.redhat.com/show_bug.cgi?id=2085361
- github.com/cri-o/cri-o