Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.9 · CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H

EPSS

• CVE-2024-10846: 0.23% estimated exploitation activity in the next 30 days; percentile 13.78 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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 Patches compose-go v2.24.1 fixed the issue Workarounds There isn't any known workaround. References https://github.com/docker/compose/issues/12235 https://github.com/compose-spec/compose-go/pull/703 https://github.com/compose-spec/compose-go/pull/618 https://github.com/docker/compose/commit/d239f0f3187a2ed5404c61f83bd5e995c81600ff#diff-33ef32bf6c23acb95f5902d7097b7a1d5128ca061167ec0716715b0b9eeaa5f6R10

Published by the source

21 Jan 2025, 20:24 UTC

Last modified by the source

28 Apr 2025, 14:09 UTC

Source last checked

26 Oct 2026, 15:09 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-36gq-35j3-p9r9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-10846

Advisory: Excessive Platform Resource Consumption within a Loop when unmarshalling Compose file having recursive loop
IDs: CVE-2024-10846, GHSA-36gq-35j3-p9r9
Record: https://patchnext.com/advisories/cve-2024-10846 (revision 1, source checked 26 Oct 2026, 15:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/compose-spec/compose-go/v2 2.4.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/compose-spec/compose-go/v2: affected >= 2.1.0, < 2.4.1; fixed in 2.4.1

## Suggested inspection (read-only)
- Go github.com/compose-spec/compose-go/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/compose-spec/compose-go/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-36gq-35j3-p9r9 (GitHub-reviewed advisory GHSA-36gq-35j3-p9r9 lists affected ranges: Go github.com/compose-spec/compose-go/v2 >=2.1.0 <2.4.1)

Commands are suggestions: review each one before running it.