Advisory record · GHSA-fcm2-6c3h-pg6j

Node DOS by way of memory exhaustion through ExecSync request in CRI-O

CVSS 7.5 HighEPSS 0.032 · 88th percentile

Published by the GitHub Advisory Database at 6 Jun 2022, 21:50 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.24.0, <1.24.1 || >=1.23.0, <1.23.3 || <1.22.51.24.1, 1.23.3, 1.22.5
Identifiers
GHSA-fcm2-6c3h-pg6j · CVE-2022-1708 · GO-2022-0480
Weakness (CWE)
CWE-400 · CWE-770
Published
6 Jun 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 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.

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
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

  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.