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

Advisory record · `GHSA-fcm2-6c3h-pg6j`

- **Identifiers:** `GHSA-fcm2-6c3h-pg6j` · `CVE-2022-1708` · `GO-2022-0480`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-400](https://cwe.mitre.org/data/definitions/400.html) · [CWE-770](https://cwe.mitre.org/data/definitions/770.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md)
- **Published:** 6 Jun 2022
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `github.com/cri-o/cri-o` (Go): affected `>=1.24.0, <1.24.1 || >=1.23.0, <1.23.3 || <1.22.5`; fixed in `1.24.1`, `1.23.3`, `1.22.5`

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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from 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](https://osv.dev/vulnerability/GHSA-fcm2-6c3h-pg6j)

## Sources

- [GitHub Advisory Database: GHSA-fcm2-6c3h-pg6j](https://github.com/advisories/GHSA-fcm2-6c3h-pg6j)
- [OSV: GHSA-fcm2-6c3h-pg6j](https://osv.dev/vulnerability/GHSA-fcm2-6c3h-pg6j)
- <https://github.com/cri-o/cri-o/security/advisories/GHSA-fcm2-6c3h-pg6j>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-1708>
- <https://github.com/cri-o/cri-o/commit/f032cf649ecc7e0c46718bd9e7814bfb317cb544>
- <https://bugzilla.redhat.com/show_bug.cgi?id=2085361>
- <https://github.com/cri-o/cri-o>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-fcm2-6c3h-pg6j>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-fcm2-6c3h-pg6j/>. Everything for agents: <https://agentprime.io/llms.txt>.
