GitHub Advisoryadvisory · Go
GHSA-6p9p-q6wh-9j89 apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams
MEDIUM
Official page ↗
- Aliases
- CVE-2026-25122
- Ecosystem
- Go
- Packages
- chainguard.dev/apko
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
- Weaknesses
- CWE-400, CWE-770
- Reviewed
- 2026-02-03
Affected packages
• Go chainguard.dev/apko: >= 0.14.8, < 1.1.0 → fixed in 1.1.0
Description
`expandapk.Split` drains the first gzip stream of an APK archive via `io.Copy(io.Discard, gzi)` without explicit bounds. With an attacker-controlled input stream, this can force large gzip inflation work and lead to resource exhaustion (availability impact).
The `Split` function reads the first tar header, then drains the remainder of the gzip stream by reading from the gzip reader directly without any maximum uncompressed byte limit or inflate-ratio cap. A caller that parses attacker-controlled APK streams may be forced to spend excessive CPU time inflating gzip data, leading to timeouts or process slowdown.
Fix: Fixed with 2be3903, Released in v1.1.0.
Acknowledgements
apko thanks Oleh Konko from 1seal for discovering and reporting this issue.
Related
Alias · CVE (1)
- CVE-2026-25122 apko allows users to build and publish OCI container images built from apk packages. vulnerability