Resource Exhaustion Affecting dagdotdev package, versions <0.0.20-r6
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-CHAINGUARDLATEST-DAGDOTDEV-15702250
- published20 Mar 2026
- disclosed4 Feb 2026
Introduced: 4 Feb 2026
CVE-2026-25122 (opens in a new tab)How to fix?
Upgrade Chainguard dagdotdev to version 0.0.20-r6 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream dagdotdev package and not the dagdotdev package as distributed by Chainguard.
See How to fix? for Chainguard relevant fixed versions and status.
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.