Is next healthy, maintained, and safe?
No — next carries 2 unpatched critical advisories and should not be adopted without a remediation plan.
The verdict
OSPulse scores next at 55/100 (medium risk), computed deterministically from live npm release history, maintainer data, and the OSV vulnerability database. No — next carries 2 unpatched critical advisories and should not be adopted without a remediation plan.
Its most recent release shipped on 25 July 2026 — 1 days ago — so development is clearly active. Across 3862 releases the cadence has been steady, which is a good sign of an ongoing maintenance rhythm. 4 maintainers are listed on npm, so the project isn't hostage to any single contributor.
OSV lists 64 known advisories for next, including 2 critical and 26 high. Open critical advisories are the strongest possible signal to pin to a patched version, replace, or fork before shipping. Each advisory is listed with its OSV/GHSA identifier below.
next is usable but carries real signals — pin versions, watch for new advisories, and keep a fallback in mind. This is a one-time snapshot of a single package — real projects depend on dozens or hundreds of packages, and any one of them can drift or be compromised between releases. Run your own package.json through the free health check, or have OSPulse monitor your whole dependency tree continuously.
Evidence trail — deterministic, auditable
Known vulnerabilities (64)
Next.js may leak x-middleware-subrequest-id to external hosts
Unexpected server crash in Next.js.
Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes
Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
Next.js Directory Traversal Vulnerability
Next.js's Middleware / Proxy redirects can be cache-poisoned
Information exposure in Next.js dev server due to lack of origin verification
Next.js: Unbounded next/image disk cache growth can exhaust storage
Next.js Improper Middleware Redirect Handling Leads to SSRF
Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
Next.js has a Middleware / Proxy bypass through dynamic route parameter injection
Next.js: Unbounded Server Action payload in Edge runtime
Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Remote Code Execution in next
Next.JS vulnerability can lead to DoS via cache poisoning
Next.js: Cache confusion of response bodies for requests with bodies
Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
Next.js Vulnerable to HTTP Request Smuggling
Next.js authorization bypass vulnerability
Next.js Allows a Denial of Service (DoS) with Server Actions
Next.js: Server-Side Request Forgery in Server Actions on custom servers
Next.js Vulnerable to Denial of Service with Server Components
Next.js: Unauthenticated disclosure of internal Server Function endpoints
Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
XSS in Image Optimization API for Next.js
- GHSA-9qr9-h5gf-34mp ↗CRITICAL
Next.js is vulnerable to RCE in React flight protocol
Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
Next.js missing cache-control header may lead to CDN caching empty reply
Authorization Bypass in Next.js Middleware
Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
Next.js Denial of Service (DoS) condition
Directory Traversal in Next.js
Next.js Server-Side Request Forgery in Server Actions
Next.js Affected by Cache Key Confusion for Image Optimization API Routes
Denial of Service condition in Next.js image optimization
Next.js: HTTP request smuggling in rewrites
Next.js Cache Poisoning
Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Next.js: Unbounded postponed resume buffering can lead to DoS
Next.js has a Denial of Service in the Image Optimization API
Next.js: null origin can bypass dev HMR websocket CSRF checks
Directory traversal vulnerability in Next.js
Next.js: Denial of Service in App Router using Server Actions
Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components
Next.js: null origin can bypass Server Actions CSRF checks
Next Vulnerable to Denial of Service with Server Components
Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Next.js has a Denial of Service with Server Components
Next.js: Denial of Service in the Image Optimization API using SVGs
Next.js Race Condition to Cache Poisoning
Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page
Next.js has a Cache poisoning vulnerability due to omission of the Vary header
Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
Open Redirect in Next.js
- GHSA-w37m-7fhw-fmv9 ↗MODERATE
Next Server Actions Source Code Exposure
Next.js vulnerable to cache poisoning in React Server Component responses
Unexpected server crash in Next.js
Denial of Service Vulnerability in next.js
Open Redirect in Next.js versions
Next.js Content Injection Vulnerability for Image Optimization
Key facts
- Latest version
- v16.2.12
- Last release
- 25 July 2026 (1 days ago)
- Total releases
- 3862
- First release
- 11 July 2011
- Package age
- 15.1 years
- Maintainers
- 4
- Known advisories
- 64
- Confidence
- High
Frequently asked
Is next still maintained?
Yes — next released as recently as 25 July 2026 (1 days ago), so it is actively maintained.
Does next have known security vulnerabilities?
Yes — OSV lists 64 advisories for next, including 2 rated critical. See the advisory list on this page for the OSV/GHSA identifiers.
Is next safe to use?
No — next carries 2 unpatched critical advisories and should not be adopted without a remediation plan. OSPulse rates it 55/100 (medium risk) based on release recency, cadence, maintainer bus factor and known vulnerabilities.
Other npm packages we've checked
next is one package. What about the other hundreds in your tree?
Paste your own package.json into the free health check for an instant snapshot — or let OSPulse monitor your whole dependency tree continuously, before your CVE scanner wakes up.
Data from the npm registry & OSV.dev · snapshot generated 2026-07-27 · scores are deterministic and recomputed on each refresh.