← Back
CVE-2026-29051
Path Traversal in chainguard.dev/melange (CVE-2026-29051)
Summary
path traversal in chainguard.dev/melange (CVE-2026-29051). Risk of unauthorized operations or information disclosure. Exploitable via ``arch``. Mitigation: upgrade to `0.43.4` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-29051** has been found in chainguard.dev/melange.
Attackers can target a specific entry point like ``arch`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade chainguard.dev/melange to **0.43.4** or later.
If unsure, ask your IT team or search "chainguard.dev/melange CVE-2026-29051" on the vendor's site.
CVE-2026-29051 (chainguard.dev/melange) — CWE-22 /
Attack vector: local / unauthenticated
Attack surface: `arch` / `pkgname` / `filepath.Separator`
Patched: `0.43.4` — apply immediately
Workaround: Do not pass `--persist-lint-results` when linting or building APKs whose `.PKGINFO` contents are not fully trusted.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in chainguard.dev/melange. Attackers reach the vulnerable code path via ``arch`` without authentication.
📍 Affected scope
chainguard.dev/melange — . Attack surface: `arch` / `pkgname` / `filepath.Separator`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.43.4**.
🛡️ Workaround
Workaround: Do not pass `--persist-lint-results` when linting or building APKs whose `.PKGINFO` contents are not fully trusted.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'chainguard.dev/melange' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'chainguard.dev/melange' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `chainguard.dev/melange` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Do not pass `--persist-lint-results` when linting or building APKs whose `.PKGINFO` contents are not fully trusted.パッチが適用されるまでの応急処置として、Do not pass `--persist-lint-results` when linting or building APKs whose `.PKGINFO` contents are not fully trusted. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade chainguard.dev/melange to 0.43.4ステージング環境で 0.43.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
chainguard.dev/melange
[{"type":"SEMVER","events":[{"introduced":"0.32.0"},{"fixed":"0.43.4"}]}]