apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams

中 5.5CVE-2026-25122 · GHSA-6p9p-q6wh-9j89 · GO-2026-4406 · 04/02/2026 公開 · 17/06/2026 更新

要点

CVE-2026-25122 は chainguard.dev/apko, apko (chainguard) に影響する深刻度「中」 (CVSS 5.5) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.13%（全脆弱性の 2.5% より高い）。
対処：1.1.0 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
chainguard.dev/apko Go	`≥ 0.14.8, < 1.1.0`	`1.1.0`
apko chainguard	`≥ 0.14.8, < 1.1.0`	`1.1.0`

概要

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.

NVD の説明

apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before 1.1.0, 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. This issue has been patched in version 1.1.0.