CVE-2026-29049: melange: unbounded HTTP download in `melange update-cache` can exhaust disk in CI
melange allows users to build apk packages using declarative pipelines. In version 0.40.5 and prior, melange update-cache downloads URIs from build configs via io.Copy without any size limit or HTTP client timeout (pkg/renovate/cache/cache.go). An attacker-controlled URI in a melange config can cause unbounded disk writes, exhausting disk on the build runne. Version 0.43.4 contains a patch.
Security readout for executives and security teams
Plain-English summary
CVE-2026-29049 affects melange, a package build tool. Older versions can download data without a size limit or timeout during `melange update-cache`. A malicious or compromised build config could fill a CI runner’s disk, disrupting builds rather than stealing data.
Executive priority
Treat this as a moderate supply-chain build reliability issue. It can interrupt CI and package production if untrusted configuration reaches build runners. Prioritize teams using melange in automated pipelines, especially where external contributors can affect build files.
Technical view
In melange 0.40.5 and prior, `pkg/renovate/cache/cache.go` used `io.Copy` for HTTP downloads without bounding response size or setting an HTTP client timeout. If a melange config points to an attacker-controlled URI, `update-cache` can write indefinitely and exhaust disk. Version 0.43.4 contains the patch.
Likely exposure
Exposure is mainly CI/CD or package-build environments running melange before 0.43.4 and processing build configs with attacker-controlled, third-party, or weakly reviewed URIs. Systems not using `melange update-cache` are less directly exposed based on the supplied sources.
Exploitation context
The supplied sources do not show active exploitation, and the CVE is not listed as KEV. Exploitation requires influencing a melange config URI and having a user or pipeline run `melange update-cache`. The documented impact is availability loss through disk exhaustion.
Researcher notes
The key evidence is vendor-reported behavior, a patch reference, and the 0.43.4 release. The source bundle identifies CWE-400 and CWE-918, but the described confirmed impact is unbounded disk write availability loss. Do not assume broader SSRF impact without vendor evidence.
Mitigation direction
Upgrade melange to version 0.43.4 or later.
Check Chainguard’s advisory and release notes for current vendor guidance.
Restrict who can modify melange build configs used in CI.
Review external URIs in build configs before running cache updates.
Set CI runner disk monitoring and failure alerts.
Validation and detection
Inventory melange versions in CI images and developer build environments.
Identify pipelines that run `melange update-cache`.
Review melange configs for untrusted or externally controlled URIs.
Confirm upgraded environments use melange 0.43.4 or later.
Check recent CI failures for disk exhaustion during cache updates.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.