# CVE-2026-102282: adm-zip extraction preserves SUID/SGID bits from untrusted ZIPs -> local privilege escalation

> Attackers can craft ZIP files to preserve SUID/SGID bits during extraction, enabling local privilege escalation to root when extracted with specific permissions.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** CLEANSTART-2026-DD82894, CLSA-2026-1790755853, CLSA-2026-1790760941, CLSA-2026-1790854753, CLSA-2026-1790856818, CLSA-2026-1790864771, CLSA-2026-1790868324, ECHO-710d-b6f5-5a85, GHSA-j5f4-cc29-5x44, MINI-2jvw-796h-6g9h, MINI-2vwp-q856-wrpr, MINI-2x2c-vjm6-2gp5, MINI-3qp2-xmhg-66xh, MINI-5226-6c2p-mjxw, MINI-86m3-8fmj-56gv, MINI-8m28-q9mg-78q9, MINI-cc24-6pvg-49jr, MINI-ch56-ffpx-f33h, MINI-h3h8-rg22-xfgc, MINI-h695-q98c-f68v, MINI-hx49-9665-m58p, MINI-jjhh-wgm9-prfc, MINI-jrvg-xh39-vxc5, ROOT-APP-NPM-CVE-2026-102282

## What is CVE-2026-102282?

CVE-2026-102282 is a high-severity vulnerability in cthackers adm-zip, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

adm-zip is a JavaScript library for creating and extracting ZIP archives in Node.js. Prior to 0.6.1, adm-zip applies the Unix permission bits stored in a zip entry directly to the extracted file via `fs.chmodSync()` when `keepOriginalPermission=true` is passed to `extractAllTo()`/`extractEntryTo()` — and it never filters the setuid/setgid/sticky bits out of those bits. A zip crafted by an attacker can therefore produce an extracted binary with mode `04755`. When extraction runs as root (the default posture in Docker builds, CI runners, and privileged install steps — the exact environments where this flag is used), the resulting root-owned setuid file is executed later by a lesser-privileged user, turning the attacker's code into a root execution. Version 0.6.1 fixes the issue.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

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-102282?

Upgrade adm-zip to 0.6.1 or later.

## Is CVE-2026-102282 being exploited?

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

Public exploit code:

- CVE-2026-102282: Local Privilege Escalation via SUID/SGID preservation during archive extraction (github_poc): https://github.com/x86byte/adm-zip_LPE-PoC
- CVE-2026-102282: adm-zip LPE via SUID/SGID preservation during archive extraction (fixed in 0.6.1) (github_poc): https://github.com/Ahmed-Elmahgob/POC-CVE-2026-102282

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102282 is a high-severity vulnerability in cthackers adm-zip, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102282 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-102282/ (Markdown: https://insights.sbomify.com/CVE-2026-102282/index.md)
```

## Sources

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

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