# apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root

Advisory record · `GHSA-qq3r-w4hj-gjp6`

- **Identifiers:** `GHSA-qq3r-w4hj-gjp6` · `CVE-2026-42574` · `GO-2026-5589`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html) · [CWE-59](https://cwe.mitre.org/data/definitions/59.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 4 May 2026
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 May 2026, 21:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `chainguard.dev/apko` (Go): affected `>=0.14.8, <1.2.5`; fixed in `1.2.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> apko versions 0.14.8 through 1.2.4 are vulnerable to a symlink-following path traversal. A crafted APK can make tar extraction write to host paths outside the build root, reachable via apko build-cpio and melange. Upgrade to apko 1.2.5; no complete workaround is listed, though using only trusted, signed APK sources reduces exposure.

Written 1 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0035, the 29th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:13 UTC: First seen by agentprime
- 31 Oct 2026, 14:13 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-qq3r-w4hj-gjp6)

## Sources

- [GitHub Advisory Database: GHSA-qq3r-w4hj-gjp6](https://github.com/advisories/GHSA-qq3r-w4hj-gjp6)
- [OSV: GHSA-qq3r-w4hj-gjp6](https://osv.dev/vulnerability/GHSA-qq3r-w4hj-gjp6)
- <https://github.com/chainguard-dev/apko/security/advisories/GHSA-qq3r-w4hj-gjp6>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-42574>
- <https://github.com/chainguard-dev/apko/pull/2187>
- <https://github.com/chainguard-dev/apko/commit/f5a96e1299ac81c7ea9441705ec467688086f442>
- <https://github.com/chainguard-dev/apko>
- <https://github.com/chainguard-dev/apko/releases/tag/v1.2.5>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-qq3r-w4hj-gjp6>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-qq3r-w4hj-gjp6/>. Everything for agents: <https://agentprime.io/llms.txt>.
