What is CVE-2026-25140?

CVE-2026-25140 is a high-severity uncontrolled resource consumption vulnerability in chainguard-dev/apko (go), affecting versions > 0.14.8, < 1.1.0. It is fixed in 1.1.0, 1.1.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2026-25140?

CVE-2026-25140 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2026-25140?

chainguard-dev/apko (go) versions > 0.14.8, = 0.14.8, < 1.1.1.

Is there a fix for CVE-2026-25140?

Yes. CVE-2026-25140 is fixed in 1.1.0, 1.1.1. Upgrade to this version or later.

Is CVE-2026-25140 exploitable, and should I be worried?

Whether CVE-2026-25140 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-25140 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-25140 in chainguard-dev/apko

Q: How severe is CVE-2026-25140?

CVE-2026-25140 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2026-25140?

chainguard-dev/apko (go) versions > 0.14.8, = 0.14.8, < 1.1.1.

Q: Is there a fix for CVE-2026-25140?

Yes. CVE-2026-25140 is fixed in 1.1.0, 1.1.1. Upgrade to this version or later.

Q: Is CVE-2026-25140 exploitable, and should I be worried?

Whether CVE-2026-25140 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-25140 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-25140?

Upgrade: chainguard-dev/apko to 1.1.0 or later, chainguard.dev/apko to 1.1.1 or later.

Summary

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

Full technical description

An attacker who controls or compromises an APK repository used by apko could cause resource exhaustion on the build host. The ExpandApk function in pkg/apk/expandapk/expandapk.go expands .apk streams without enforcing decompression limits, allowing a malicious repository to serve a small, highly-compressed .apk that inflates into a large tar stream, consuming excessive disk space and CPU time, causing build failures or denial of service.

Fix: Fixed in 2be3903. Released in 1.1.0.

Acknowledgements

apko thanks Oleh Konko (@1seal) from 1seal for discovering and reporting this issue.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2026-25140 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.0, 1.1.1); upgrading removes the vulnerable code path.

Affected versions

chainguard-dev/apko (> 0.14.8, < 1.1.0) chainguard.dev/apko (>= 0.14.8, < 1.1.1)

Security releases

chainguard-dev/apko → 1.1.0 (go) chainguard.dev/apko → 1.1.1 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

chainguard-dev/apko to 1.1.0 or later; chainguard.dev/apko to 1.1.1 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-25140? CVE-2026-25140 is a high-severity uncontrolled resource consumption vulnerability in chainguard-dev/apko (go), affecting versions > 0.14.8, < 1.1.0. It is fixed in 1.1.0, 1.1.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2026-25140? CVE-2026-25140 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2026-25140?
- chainguard-dev/apko (go) (versions > 0.14.8, < 1.1.0)
- chainguard.dev/apko (go) (versions >= 0.14.8, < 1.1.1)
Is there a fix for CVE-2026-25140? Yes. CVE-2026-25140 is fixed in 1.1.0, 1.1.1. Upgrade to this version or later.
Is CVE-2026-25140 exploitable, and should I be worried? Whether CVE-2026-25140 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-25140 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-25140?
- Upgrade chainguard-dev/apko to 1.1.0 or later
- Upgrade chainguard.dev/apko to 1.1.1 or later