next@16.4.2
Skip this version — install 16.4.6 instead.
7 known advisories (worst: moderate), fixed in 16.4.5.
Why this verdict
- 7 known advisories (worst: moderate), fixed in 16.4.5.Evidence
Confidence 100% · algorithm v1 · computed 2026-11-22. How verdicts work
Supply chain and security
- Malware reports
- None known (OSV)
- Known advisories
- 7 known
- License
- MIT
- Install scripts
- None
- Build provenance
- Signed provenance
- Weekly downloads
- 6,705,810
- GHSA-7qx7-33qx-rqx2Next.js: SVG rejection bypass in the image optimization
- GHSA-f3mh-rxg3-f5g2Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
- GHSA-mfr8-8qww-v76hNext.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
- GHSA-pc58-hwjq-p385Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
- GHSA-rhh4-g77r-r9qjNext.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
- GHSA-vc7v-qv4w-wrv8Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
- GHSA-vvgp-ww4w-46vfNext.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
Compatibility
No compatibility boundary is crossed: this is a patch or minor release on a stable major.
38 issues mention this version in vercel/next.js within 14 days of release. See them on GitHub
Check the official release notes below for behaviour changes before merging.
Release notes
Read the Next.js changelog on Changes.Watch or the package page on npm for this version’s features and fixes.
Deprecations and deadlines
The maintainer has not deprecated this version on npm.
Did upgrading to 16.4.2 work for you?
Results appear once three developers have voted.