Is chainguard.dev/apko 0.30 vulnerable?
Go · 36 releases from 0.30.0 to 0.30.35 · latest chainguard.dev/apko is 1.5.1 · checked 18 Nov 2026
Yes: 13 known advisories
Yes. chainguard.dev/apko 0.30.35, the last 0.30 release, is affected by 13 known security advisories (4 high, 2 medium, 7 low), including CVE-2026-54174, CVE-2026-42575, CVE-2026-42574. Upgrade to 1.2.9 or later to fix all of them.
go get chainguard.dev/apko@v1.2.9Is your project on an affected chainguard.dev/apko?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting chainguard.dev/apko 0.30.35
melange: Incomplete package integrity verification allows data section substitution in chainguard.dev/apko
- Affected
- <1.2.9
- Fixed in
- 1.2.9
melange: Incomplete package integrity verification allows data section substitution
- Affected
- <1.2.9
- Fixed in
- 1.2.9
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root in chainguard.dev/apko
- Affected
- >=0.14.8 <1.2.5
- Fixed in
- 1.2.5
apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible) in chainguard.dev/apko
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery in chainguard.dev/apko
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
- Affected
- >=0.14.8 <1.2.5
- Fixed in
- 1.2.5
apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko affected by potential unbounded resource consumption in expandapk.ExpandApk on attacker-controlled .apk streams in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.1
- Fixed in
- 1.1.1
apko has a path traversal in apko dirFS which allows filesystem writes outside base in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko has a path traversal in apko dirFS which allows filesystem writes outside base
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
Every chainguard.dev/apko 0.30.x release
Affected: 0.30.0 to 0.30.35. Latest chainguard.dev/apko: 1.5.1.
| Version | Known advisories |
|---|---|
| chainguard.dev/apko 0.30.35 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.34 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.33 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.32 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.31 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.30 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.29 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.28 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.27 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.26 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.25 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.24 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.23 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.22 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.21 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.20 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.19 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.18 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.17 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.16 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.15 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.14 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.13 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.12 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.11 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.10 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.9 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.8 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.7 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.6 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.5 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.4 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.3 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.2 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.1 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
| chainguard.dev/apko 0.30.0 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42574, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42574, CVE-2026-42576, CVE-2026-25140, CVE-2026-25121, CVE-2026-25122, CVE-2026-25122, CVE-2026-25121 |
Which of your client projects are still on chainguard.dev/apko 0.30?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact chainguard.dev/apko version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other chainguard.dev/apko versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Go registry. Refreshed daily.