CVE-2024-10846
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe compose-go library (v2.10-v2.4.0) and Docker Compose (v2.27.0-v2.29.7) are vulnerable to resource exhaustion via malicious YAML payloads. An authenticated attacker can send specially crafted YAML that causes excessive memory allocation and CPU consumption during parsing, leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Docker Compose versionRun 'docker compose version' or 'docker-compose version' to see the installed versionAffected if Version is between v2.27.0 and v2.29.7 inclusive
-
Identify compose-go library usageSearch project dependency files (go.mod, package.json, requirements.txt, etc.) for the compose-go library and note its versionAffected if compose-go library version is between v2.10 and v2.4.0 (or falls within this range)
-
Verify YAML parsing is accessibleCheck if there are any endpoints, APIs, or interfaces that accept YAML input for processing (look for YAML parsing code, upload functionality, or compose file processing)Affected if YAML parsing functionality is exposed or enabled in the environment
-
Confirm authentication is required for YAML processingReview access controls, API authentication requirements, or user privileges needed to submit YAML payloads to the systemAffected if YAML parsing endpoints are accessible without authentication or to low-privilege users
You are affected if Docker Compose v2.27.0-v2.29.7 or compose-go library v2.10-v2.4.0 is in use AND the system accepts YAML input that gets parsed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate compose-go to a patched version beyond v2.4.0 and Docker Compose to v2.29.8 or later. Consider implementing YAML payload size limits and parsing timeouts as defense-in-depth measures.
compose-go v2.4.1 or later (or Docker Compose v2.29.8+)
- 1. Identify the compose-go library version in your project by checking your dependency files (e.g., go.mod, package.json, or similar)
- 2. Locate where compose-go is used as a dependency - it may be a transitive dependency through Docker Compose
- 3. If directly depending on compose-go, update the dependency to version v2.4.1 or later
- 4. If using Docker Compose, ensure you are using version v2.29.8 or later which includes the fixed compose-go library
- 5. Run your build/dependency resolution to confirm the updated version is resolved
- 6. Test your application to verify normal operation after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-10846 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-10846 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data