Path Traversal in chainguard.dev/apko (CVE-2026-42574)
Summary
Path traversal in chainguard.dev/apko (CVE-2026-42574). Data can be tampered with by attackers. Exploitable via TypeSymlink. Mitigation: upgrade to 1.2.5 or later.
Original description
The description as published by the source.
apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before version 1.2.5, a crafted .apk could install a TypeSymlink tar entry whose target pointed outside the build root, and a subsequent directory-creation or file-write entry in the same or later archive could traverse that symlink to reach host paths the build user could write to. This issue has been patched in version 1.2.5.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42574 has been found in chainguard.dev/apko.
Attackers can target a specific entry point like TypeSymlink over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.5/10.
What to do: upgrade chainguard.dev/apko to 1.2.5 or later.
If unsure, ask your IT team or search "chainguard.dev/apko CVE-2026-42574" on the vendor's site.
CVE-2026-42574 (chainguard.dev/apko) — CWE-22 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: TypeSymlink / sanitizePath / DirFS / ReadFile
Patched: 1.2.5 — apply immediately
Workaround: No complete workaround.
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.
Path traversal (CWE-22) exists in chainguard.dev/apko. Attackers reach the vulnerable code path via TypeSymlink without authentication.
Check the vendor advisory for the affected versions of chainguard.dev/apko. Attack surface: TypeSymlink / sanitizePath / DirFS / ReadFile.
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers.
Update to 1.2.5.
Workaround: No complete workaround.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'chainguard.dev/apko' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'chainguard.dev/apko' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
chainguard.dev/apkoを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
No complete workaround.パッチが適用されるまでの応急処置として、No complete workaround. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade chainguard.dev/apko to 1.2.5ステージング環境で 1.2.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com