melange QEMU runner could write files outside workspace directoryGHSA-qxx2-7h4c-83f4
HIGHFix: chainguard-dev/melange@6e243d0GHSA-qxx2-7h4c-83f4 is a high-severity (CVSS 8.2) Path Traversal vulnerability in chainguard.dev/melange. A fix is available for chainguard.dev/melange — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-qxx2-7h4c-83f4.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
chainguard.dev/melangeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An attacker who can influence the tar stream from a QEMU guest VM could write files outside the intended workspace directory on the host. The retrieveWorkspace function extracts tar entries without validating that paths stay within the workspace, allowing Path Traversal via ../ sequences.
Fix: Fixed in 6e243d0d. Merged in release.
Acknowledgements
melange thanks Oleh Konko from 1seal for discovering and reporting this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | chainguard.dev/melange | ≥ 0.11.3&&< 0.40.3 | 0.40.3go get chainguard.dev/melange@v0.40.3 |
Affected Products
melangechainguardDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for chainguard.dev/melange, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update chainguard.dev/melange to 0.40.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qxx2-7h4c-83f4 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is GHSA-qxx2-7h4c-83f4 in your dependencies?
Find it across Go, including transitive dependencies.