How severe is CVE-2026-25122?

CVE-2026-25122 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2026-25122 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-25122?

CVE-2026-25122 affects Chainguard Apko. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-25122?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-25122 have an EU (EUVD) identifier?

Yes. CVE-2026-25122 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5379.

When was CVE-2026-25122 published?

CVE-2026-25122 was published on 2026-02-04 and last updated on 2026-06-17.

CVE-2026-25122

CVE-2026-25122 is a medium-severity vulnerability in Chainguard Apko with a CVSS 3.x base score of 5.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-770.

Key facts

Severity: Medium (CVSS 3.x base score 5.5)
EPSS exploit prediction: 0% (1st percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-5379
Weakness: CWE-770
Affected product: Chainguard Apko
Published: 2026-02-04
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2026-25122?: 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.
How severe is CVE-2026-25122?: CVE-2026-25122 has a CVSS 3.x base score of 5.5, rated medium severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2026-25122 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-25122?: CVE-2026-25122 affects Chainguard Apko. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-25122?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-25122 have an EU (EUVD) identifier?: Yes. CVE-2026-25122 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-5379.
When was CVE-2026-25122 published?: CVE-2026-25122 was published on 2026-02-04 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:chainguard:apko:*:*:*:*:*:go:*:*

More vulnerabilities in Chainguard Apko

CVE-2026-25140 — High (CVSS 7.5): apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before…
CVE-2026-25121 — High (CVSS 7.5): apko allows users to build and publish OCI container images built from apk packages. From version 0.14.8 to before…

All CVEs affecting Chainguard Apko →

Other CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities

CVE-2026-31283 — Critical (CVSS 9.8): In Totara LMS v19.1.5 and before, the forgot password API does not implement rate limiting for the target email…
CVE-2020-37067 — Critical (CVSS 9.8): Filetto 1.0 FTP server contains a denial of service vulnerability in the FEAT command processing that allows attackers…
CVE-2021-47875 — Critical (CVSS 9.8): GeoGebra CAS Calculator 6.0.631.0 contains a denial of service vulnerability that allows attackers to crash the…
CVE-2025-11832 — Critical (CVSS 9.8): Allocation of Resources Without Limits or Throttling vulnerability in Azure Access Technology BLU-IC2, Azure Access…
CVE-2024-44241 — Critical (CVSS 9.8): The issue was addressed with improved bounds checks. This issue is fixed in iOS 18.1 and iPadOS 18.1, macOS Sequoia…
CVE-2022-3439 — Critical (CVSS 9.8): Allocation of Resources Without Limits or Throttling in GitHub repository ikus060/rdiffweb prior to 2.5.0.

Browse all CWE-770 (Allocation of Resources Without Limits or Throttling) vulnerabilities →