undici@7.22.0 has 2 high-severity advisories (via @vercel/sandbox)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 287
- Forks
- 58
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 17
Description
Summary
npm audit on vercel-plugin@0.42.1 (and 0.40.1) reports two high-severity advisories in undici@7.22.0, pulled in transitively via @vercel/sandbox@1.8.0:
vercel-plugin@0.42.1
└─┬ @vercel/sandbox@1.8.0
└── undici@7.22.0
Advisories:
- GHSA-4992-7rv2-5pvq — CRLF injection via
upgradeoption (high) - GHSA-phc3-fgpg-7m6h — Unbounded memory consumption in
DeduplicationHandler→ DoS (high) - GHSA-v9p9-hfj2-hcw8 — Unhandled exception in WebSocket client on invalid
server_max_window_bits(moderate)
Each has a fixed version available; npm audit fix resolves all three without breaking changes.
Reproduction
cd ~/.claude/plugins/cache/claude-plugins-official/vercel/0.42.1
npm i --package-lock-only --ignore-scripts
npm audit
2 high severity vulnerabilities
fix available via `npm audit fix`
Suggested fix
Bump @vercel/sandbox to a release that pulls a patched undici, or add an overrides entry in the plugin's package.json to pin undici to the fixed version.
Impact
Practical risk is low for typical plugin use (calls go to Vercel's own APIs, not arbitrary URLs), but npm audit flags it on every install of the plugin, which is noisy for users running supply-chain hygiene tools.
Reported via Claude Code while auditing installed plugins for compromised packages — signatures all verified clean, no compromise indicators, just these known CVEs.
Contributor guide
No contributing guide indexed for this repository
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 with the plugin's package.json and inspect the dependency path through @vercel/sandbox to undici. Reproduce the report with npm i --package-lock-only --ignore-scripts and npm audit; done means the patched dependency is selected and npm audit no longer reports these advisories without breaking the plugin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- security
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100