# CVE-2026-114103: adm-zip 0.6.0 Decompression Bomb Guard Bypass via getDataAsync()


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** CLEANSTART-2026-FU01230, ECHO-2ab8-f491-d1d7, GHSA-c6fg-446q-cg94, GHSA-x5pg-q574-6h2m, MINI-2r7j-vx6f-pqxr, MINI-4493-xg2f-2q39, MINI-476c-9m84-q2v8, MINI-6f9f-rw69-gp8f, MINI-82q9-qq92-73f9, MINI-9w4g-pg9w-xqvg, MINI-hx59-jg87-26f8, MINI-j34m-qf98-rmfh, MINI-m2v5-mr47-gqh8, MINI-mchx-fh9f-j83x, MINI-q4f9-x7vj-5m4m, MINI-r2m8-g4jw-xv5x, MINI-r94g-fpvp-wf2c, MINI-vvxh-7q3g-rqrc

## What is CVE-2026-114103?

CVE-2026-114103 is a medium-severity vulnerability in cthackers adm-zip, published on 21 Oct 2026. 

### Official description

adm-zip 0.6.0 contains a decompression bomb protection bypass that allows attackers to evade the maxOutputLength guard by targeting the asynchronous getDataAsync() path in methods/inflater.js. Attackers can craft ZIP entries with falsified small declared sizes and high-ratio DEFLATE payloads to exhaust memory in applications reading entries asynchronously.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-114103?

2 open source packages ship an affected version, including adm-zip.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `adm-zip` | npm | All versions | 0.6.1 |
| `adm-zip` | npm | All versions | 0.6.1 |

## How do I fix CVE-2026-114103?

Upgrade adm-zip to 0.6.1 or later.

## Is CVE-2026-114103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114103 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-114103 and fix it if it is affected.

What it is: CVE-2026-114103 is a medium-severity vulnerability in cthackers adm-zip, published on 21 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-114103 exists.

Affected packages and fixed versions:
- adm-zip (npm): affected all versions; fixed in 0.6.1
- adm-zip (npm): affected all versions; fixed in 0.6.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-114103/ (Markdown: https://insights.sbomify.com/CVE-2026-114103/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-114103
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-114103
- OSV: https://osv.dev/vulnerability/CVE-2026-114103

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-114103/
Summaries are generated and may contain mistakes; the official description above is the record.