CVE-2026-42574
published 2026-05-09CVE-2026-42574: 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…
PriorityP346high7.5CVSS 3.1
AVNACLPRNUINSUCNIHAN
EPSS
0.35%
27.5th percentile
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.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chainguard-dev | apko | — | — |
| chainguard.dev | apko | >= 0.14.8 < 1.2.5 | 1.2.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
chainguard-dev apko 0.14.5/1.1.0/1.1.1 pkg/apk/fs/rwosfs.go dirFS path traversal (EUVD-2026-28932)
vuldb·2026-05-10·CVSS 7.5
CVE-2026-42574 [HIGH] chainguard-dev apko 0.14.5/1.1.0/1.1.1 pkg/apk/fs/rwosfs.go dirFS path traversal (EUVD-2026-28932)
A vulnerability, which was classified as critical, was found in chainguard-dev apko 0.14.5/1.1.0/1.1.1. The impacted element is the function dirFS of the file pkg/apk/fs/rwosfs.go. The manipulation results in path traversal.
This vulnerability is cataloged as CVE-2026-42574. The attack may be launched remotely. There is no exploit available.
You should upgrade the affected component.
GHSA
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
ghsa·2026-05-04
CVE-2026-42574 [HIGH] CWE-22 apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
### Impact
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. The root cause was the `sanitizePath` helper in `pkg/apk/fs/rwosfs.go`, which rejected only lexical `..` traversal and did not resolve or refuse symlinks. Every disk-backed `DirFS` method that handed its caller-supplied path to a symlink-following stdlib call — `ReadFile`, `WriteFile`, `Chmod`, `Chown`, `Chtimes`, `MkdirAll`, `Mkdir`, and `Mknod` — was affected. The reachable primitive from a malicious APK du
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-05-09
Published