Advisory

GHSA-6p9p-q6wh-9j89

Also known as: CVE-2026-25122, GO-2026-4406

Summary

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

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2026-02-03 23:58 UTC
Modified
2026-09-10 03:49 UTC

Affected packages and fixes

chainguard.dev/apko

Go · All systems

Affected

  • introduced 0.14.8, fixed 1.1.0 (semver)

Fixed versions

1.1.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences