Is chainguard.dev/apko 1.1 vulnerable?
Go · 17 releases from 1.1.0 to 1.1.16 · latest chainguard.dev/apko is 1.5.1 · checked 18 Nov 2026
Yes: 8 known advisories
Yes. chainguard.dev/apko 1.1.16, the last 1.1 release, is affected by 8 known security advisories (3 high, 1 medium, 4 low), including CVE-2026-54174, CVE-2026-42575, CVE-2026-42574. 1 more affects earlier 1.1.x releases. 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 1.1.16
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
Fixed within 1.1.x, affecting earlier releases
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
Every chainguard.dev/apko 1.1.x release
Affected: 1.1.0 to 1.1.16. Latest chainguard.dev/apko: 1.5.1.
| Version | Known advisories |
|---|---|
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
| chainguard.dev/apko 1.1.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 |
Which of your client projects are still on chainguard.dev/apko 1.1?
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.