Is chainguard.dev/apko 1.2 vulnerable?
Go · 46 releases from 1.2.0 to 1.2.45 · latest chainguard.dev/apko is 1.5.1 · checked 18 Nov 2026
No known advisories in the last release
chainguard.dev/apko 1.2.45, the last 1.2 release, has no known advisories. 8 advisories affect earlier 1.2.x releases, so update to 1.2.45.
go get chainguard.dev/apko@v1.2.45Is 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
Fixed within 1.2.x, affecting earlier releases
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
Every chainguard.dev/apko 1.2.x release
Affected: 1.2.0 to 1.2.8. 1.2.9 and later are not affected. Latest chainguard.dev/apko: 1.5.1.
| Version | Known advisories |
|---|---|
| chainguard.dev/apko 1.2.45 | None |
| chainguard.dev/apko 1.2.44 | None |
| chainguard.dev/apko 1.2.43 | None |
| chainguard.dev/apko 1.2.42 | None |
| chainguard.dev/apko 1.2.41 | None |
| chainguard.dev/apko 1.2.40 | None |
| chainguard.dev/apko 1.2.39 | None |
| chainguard.dev/apko 1.2.38 | None |
| chainguard.dev/apko 1.2.37 | None |
| chainguard.dev/apko 1.2.36 | None |
| chainguard.dev/apko 1.2.35 | None |
| chainguard.dev/apko 1.2.34 | None |
| chainguard.dev/apko 1.2.33 | None |
| chainguard.dev/apko 1.2.32 | None |
| chainguard.dev/apko 1.2.31 | None |
| chainguard.dev/apko 1.2.30 | None |
| chainguard.dev/apko 1.2.29 | None |
| chainguard.dev/apko 1.2.28 | None |
| chainguard.dev/apko 1.2.27 | None |
| chainguard.dev/apko 1.2.26 | None |
| chainguard.dev/apko 1.2.25 | None |
| chainguard.dev/apko 1.2.24 | None |
| chainguard.dev/apko 1.2.23 | None |
| chainguard.dev/apko 1.2.22 | None |
| chainguard.dev/apko 1.2.21 | None |
| chainguard.dev/apko 1.2.20 | None |
| chainguard.dev/apko 1.2.19 | None |
| chainguard.dev/apko 1.2.18 | None |
| chainguard.dev/apko 1.2.17 | None |
| chainguard.dev/apko 1.2.16 | None |
| chainguard.dev/apko 1.2.15 | None |
| chainguard.dev/apko 1.2.14 | None |
| chainguard.dev/apko 1.2.13 | None |
| chainguard.dev/apko 1.2.12 | None |
| chainguard.dev/apko 1.2.11 | None |
| chainguard.dev/apko 1.2.10 | None |
| chainguard.dev/apko 1.2.9 | None |
| chainguard.dev/apko 1.2.8 | CVE-2026-54174, CVE-2026-54174 |
| chainguard.dev/apko 1.2.7 | CVE-2026-54174, CVE-2026-54174 |
| chainguard.dev/apko 1.2.6 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42576 |
| chainguard.dev/apko 1.2.5 | CVE-2026-54174, CVE-2026-54174, CVE-2026-42575, CVE-2026-42576, CVE-2026-42575, CVE-2026-42576 |
| chainguard.dev/apko 1.2.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.2.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.2.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.2.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.2.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 |
Which of your client projects are still on chainguard.dev/apko 1.2?
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.