CVE-2026-25122: apko is vulnerable to unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams

Published Feb 3, 2026
·
Updated

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.

Other sources

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.

— MITRE

Affected Software

2 affected componentsFixes available
go/chainguard.dev/apko>=0.14.8<1.1.0
1.1.0
chainguard Apko Go>=0.14.8<1.1.0

Event History

Feb 3, 2026
Advisory Published
via GitHub·11:58 PM
Data Sourced
via GitHub·11:58 PM
DescriptionSeverityWeaknessAffected Software
Feb 4, 2026
CVE Published
via MITRE·07:02 PM
Data Sourced
via MITRE·07:02 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 PM
RemedyAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-25122?

CVE-2026-25122 is classified as a high-severity vulnerability due to its potential for unbounded resource consumption.

2

How do I fix CVE-2026-25122?

To fix CVE-2026-25122, update to version 1.1.0 or later of the apko package.

3

What kind of attack does CVE-2026-25122 facilitate?

CVE-2026-25122 facilitates denial-of-service attacks by causing excessive resource consumption.

4

What software is affected by CVE-2026-25122?

CVE-2026-25122 affects versions of the apko package prior to 1.1.0.

5

How does CVE-2026-25122 exploit gzip streams?

CVE-2026-25122 exploits gzip streams by draining data without applying explicit bounds, allowing for large data consumption.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203