{"id":"EUVD-2026-25355","enisaUuid":"94ca5439-5da2-36c8-97b8-0809c24dde04","description":"melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, an attacker who can influence a melange configuration file — for example through pull-request-driven CI or build-as-a-service scenarios — could set `pipeline[].uses` to a value containing `../` sequences or an absolute path. The `(*Compiled).compilePipeline` function in `pkg/build/compile.go` passed `uses` directly to `filepath.Join(pipelineDir, uses + \".yaml\")` without validating the value, so the resolved path could escape each `--pipeline-dir` and read an arbitrary YAML-parseable file visible to the melange process. Because the loaded file is subsequently interpreted as a melange pipeline and its `runs:` block is executed via `/bin/sh -c` in the build sandbox, this additionally allowed shell commands sourced from an out-of-tree file to run during the build, bypassing the review boundary that normally covers the in-tree pipeline definition. The issue is fixed in melange v0.43.4 via commit 5829ca4. The fix rejects `uses` values that are absolute paths or contain `..`, and verifies (via `filepath.Rel` after `filepath.Clean`) that the resolved target remains within the pipeline directory. As a workaround, only run `melange build` against configuration files from trusted sources. In CI systems that build user-supplied melange configs, gate builds behind manual review of `pipeline[].uses` values and reject any containing `..` or leading `/`.","datePublished":"Apr 23, 2026, 11:58:39 PM","dateUpdated":"Apr 25, 2026, 1:38:30 AM","baseScore":6.1,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N","references":"https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9\n","aliases":"CVE-2026-29050\nGHSA-98f2-w9h9-7fp9\n","assigner":"GitHub_M","epss":0.14,"enisaIdProduct":[{"id":"13207452-c055-37f2-a0e7-e52f1c8a9d28","product":{"name":"melange","vendor":{"name":"chainguard-dev"}},"product_version":"0.32.0, \u003c 0.43.4"}],"enisaIdVendor":[{"id":"06ce7c64-2828-383d-adfc-cce7439d9576","vendor":{"name":"chainguard-dev"}}],"enisaIdVulnerability":[{"id":"257c9665-deb1-331b-b6bb-0d06223d9ba3","vulnerability":{"id":"GHSA-98f2-w9h9-7fp9","description":"melange has Path Traversal When Resolving External Pipelines via Unvalidated pipeline[].uses","datePublished":"Apr 23, 2026, 9:53:33 PM","dateUpdated":"Apr 27, 2026, 4:34:36 PM","baseScore":0.0,"references":"https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9\nhttps://nvd.nist.gov/vuln/detail/CVE-2026-29050\nhttps://github.com/chainguard-dev/melange/commit/5829ca45cfe14dfeb73ffb716992db3b1b7892ac\nhttps://github.com/chainguard-dev/melange\n","enisa_id":"EUVD-2026-25355\n","aliases":"CVE-2026-29050\nGHSA-98f2-w9h9-7fp9\n","epss":0.0,"dataProcessed":"Oct 25, 2026, 1:55:10 AM","vulnerabilityProduct":[],"vulnerabilityVendor":[]}},{"id":"80d03b51-18ac-34c5-bf78-c1b2962f86c6","vulnerability":{"id":"CVE-2026-29050","description":"melange allows users to build apk packages using declarative pipelines. Starting in version 0.32.0 and prior to version 0.43.4, an attacker who can influence a melange configuration file — for example through pull-request-driven CI or build-as-a-service scenarios — could set `pipeline[].uses` to a value containing `../` sequences or an absolute path. The `(*Compiled).compilePipeline` function in `pkg/build/compile.go` passed `uses` directly to `filepath.Join(pipelineDir, uses + \".yaml\")` without validating the value, so the resolved path could escape each `--pipeline-dir` and read an arbitrary YAML-parseable file visible to the melange process. Because the loaded file is subsequently interpreted as a melange pipeline and its `runs:` block is executed via `/bin/sh -c` in the build sandbox, this additionally allowed shell commands sourced from an out-of-tree file to run during the build, bypassing the review boundary that normally covers the in-tree pipeline definition. The issue is fixed in melange v0.43.4 via commit 5829ca4. The fix rejects `uses` values that are absolute paths or contain `..`, and verifies (via `filepath.Rel` after `filepath.Clean`) that the resolved target remains within the pipeline directory. As a workaround, only run `melange build` against configuration files from trusted sources. In CI systems that build user-supplied melange configs, gate builds behind manual review of `pipeline[].uses` values and reject any containing `..` or leading `/`.","datePublished":"Apr 23, 2026, 11:58:39 PM","dateUpdated":"Apr 25, 2026, 1:38:30 AM","status":"PUBLISHED","baseScore":6.1,"baseScoreVersion":"3.1","baseScoreVector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N","references":"https://github.com/chainguard-dev/melange/security/advisories/GHSA-98f2-w9h9-7fp9\n","enisa_id":"EUVD-2026-25355\n","assigner":"GitHub_M","epss":0.14,"dataProcessed":"Oct 29, 2026, 7:19:51 AM","vulnerabilityProduct":[{"id":"6fdabc98-22fe-351a-ad07-9568889de8df","product":{"name":"melange","vendor":{"name":"chainguard-dev"}},"product_version":"0.32.0, \u003c 0.43.4"}],"vulnerabilityVendor":[{"id":"fca3c41c-916b-3a4e-b126-1b2f514645e2","vendor":{"name":"chainguard-dev"}}]}}],"enisaIdAdvisory":[]}