{"id":"CVE-2026-29051","summary":"melange has Path Traversal via .PKGINFO in --persist-lint-results","details":"melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, `melange lint --persist-lint-results` (opt-in flag, also usable via `melange build --persist-lint-results`) constructs output file paths by joining `--out-dir` with the `arch` and `pkgname` values read from the `.PKGINFO` control file of the APK being linted. In affected versions these values were not validated for path separators or `..` sequences, so an attacker who can supply an APK to a melange-based lint/build pipeline (e.g. CI that lints third-party APKs, or build-as-a-service) could cause melange to write `lint-\u003cpkgname\u003e-\u003cpkgver\u003e-r\u003cepoch\u003e.json` to an arbitrary `.json` path reachable by the melange process. The written file is a JSON lint report whose content is partially attacker-influenced. There is no direct code-execution path, but the write can clobber other JSON artifacts on the filesystem. The issue only affects deployments that explicitly pass `--persist-lint-results`; the flag is off by default. The issue is fixed in melange v0.43.4 by validating `arch` and `pkgname` for `..`, `/`, and `filepath.Separator` before path construction in `pkg/linter/results.go` (commit 84f3b45). As a workaround, do not pass `--persist-lint-results` when linting or building APKs whose `.PKGINFO` contents are not fully trusted. Running melange as a low-privileged user and confining writes to an isolated directory also limits impact.","aliases":["GHSA-q2pw-xx38-p64j","GO-2026-5562"],"modified":"2026-08-12T03:51:49.095970255Z","published":"2026-04-24T00:00:36.253Z","related":["openSUSE-SU-2026:21483-1"],"database_specific":{"cwe_ids":["CWE-22"],"osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/29xxx/CVE-2026-29051.json","cna_assigner":"GitHub_M"},"references":[{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/29xxx/CVE-2026-29051.json"},{"type":"ADVISORY","url":"https://github.com/chainguard-dev/melange/security/advisories/GHSA-q2pw-xx38-p64j"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-29051"},{"type":"FIX","url":"https://github.com/chainguard-dev/melange/commit/84f3b450ce6e472c4abb8dc4c26d0ce8ac1259ac"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/chainguard-dev/melange","events":[{"introduced":"5307b483f36d3099f17a1db338779be6a5f0b9cf"},{"fixed":"ba26216d9671b7fd8e2696a3a217f441f2e04b05"},{"fixed":"84f3b450ce6e472c4abb8dc4c26d0ce8ac1259ac"}],"database_specific":{"extracted_events":[{"introduced":"0.32.0"},{"fixed":"0.43.4"}],"source":["CPE_RANGE","REFERENCES"],"cpe":"cpe:2.3:a:chainguard:melange:*:*:*:*:*:go:*:*"}}],"versions":["v0.43.3","v0.43.2","v0.43.1","v0.43.0","v0.42.0","v0.41.1","v0.41.0","v0.40.5","v0.40.4","v0.40.3","v0.40.2","v0.40.1","v0.40.0","v0.39.0","v0.38.1","v0.38.0","v0.37.5","v0.37.4","v0.37.3","v0.37.2","v0.37.1","v0.37.0","v0.36.0","v0.35.1","v0.35.0","v0.34.3","v0.34.2","v0.34.1","v0.34.0","v0.33.2","v0.33.1","v0.33.0","v0.32.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-29051.json"}}],"schema_version":"1.9.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L"}]}