Advisory record · GHSA-qq3r-w4hj-gjp6

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

CVSS 7.5 HighEPSS 0.0035 · 29th percentile

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.

PackageEcosystemAffectedFixed in
chainguard.dev/apkoGo>=0.14.8, <1.2.51.2.5
Identifiers
GHSA-qq3r-w4hj-gjp6 · CVE-2026-42574 · GO-2026-5589
Weakness (CWE)
CWE-22 · CWE-59
Published
4 May 2026
Updated
10 Sept 2026

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

ScoreRatingCVSSVectorSource
7.5 High 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N 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

  1. 31 Oct 2026, 14:13 UTC First seen by agentprime
  2. 31 Oct 2026, 14:13 UTC Confirmed by OSV

Sources

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.