max-mapper / max-mapper/extract-zip
CVE-2026-56876 — patched release planned? (downstream consumer)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 398
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
Hi maintainers,
We use extract-zip transitively (via @puppeteer/browsers → Puppeteer →
Lighthouse CI) in our CI tooling. Dependabot flags CVE-2026-56876 /
GHSA-jmr9-qjv8-65gv ("unvalidated symlink path traversal", high severity).
The advisory marks <= 2.0.1 as vulnerable, and 2.0.1 is the latest
published version, so there is no patched release to upgrade to.
Is a fix/release planned? If so, is there a branch or PR we can track?
If maintainer bandwidth is the blocker, we're happy to contribute — a
symlink/path-validation guard on zip-entry extraction is a small change
and we can open a PR with a test. Just let us know the preferred approach.
Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing CVE-2026-56876/GHSA-jmr9-qjv8-65gv and the zip-entry extraction path in extract-zip. Confirm the expected symlink/path-validation behavior and identify suitable coverage for the guard; done means the vulnerability is addressed, a test demonstrates the protection, and a patched release can be prepared.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100