Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
Next.js security fixes
84 fixes · 35 high/criticalSource: GitHub Advisory Database, pulled hourly. · Last checked Nov 19, 2026
Next.js: SVG rejection bypass in the image optimization
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays
next.js cache leak across root param values in nested 'use cache' functions
Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
Show all 74 ↓
Next.js: Denial of Service in App Router using Server Actions
Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages
Next.js has cache poisoning of SSG and ISR pages in self-hosted applications
Next.js has information disclosure in development server's Model Context Protocol endpoint
Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass
Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
Next.js has Server-Side Request Forgery in Image Optimization
Next.js: Remote Code Execution in next/og ImageResponse
Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
Next.js: Unauthenticated Remote Code Execution on windows-hosted servers
Next.js: Server-Side Request Forgery in Server Actions on custom servers
Next.js: Cache confusion of response bodies for requests with bodies
Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
Next.js: Unbounded Server Action payload in Edge runtime
Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Next.js: Denial of Service in the Image Optimization API using SVGs
Next.js: Unauthenticated disclosure of internal Server Function endpoints
Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
Next.js: Denial of Service in App Router using Server Actions
Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
Next.js's Middleware / Proxy redirects can be cache-poisoned
Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components
Next.js has a Denial of Service in the Image Optimization API
Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
Next.js vulnerable to cache poisoning in React Server Component responses
Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes
Next.js has a Middleware / Proxy bypass through dynamic route parameter injection
Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
Next.js Vulnerable to Denial of Service with Server Components
Next.js has a Denial of Service with Server Components
Next.js: HTTP request smuggling in rewrites
Next.js: Unbounded next/image disk cache growth can exhaust storage
Next.js: Unbounded postponed resume buffering can lead to DoS
Next.js: null origin can bypass Server Actions CSRF checks
Next.js: null origin can bypass dev HMR websocket CSRF checks
Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Next.js has Unbounded Memory Consumption via PPR Resume Endpoint
Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
Next has a Denial of Service with Server Components - Incomplete Fix Follow-Up
Next Server Actions Source Code Exposure
Next Vulnerable to Denial of Service with Server Components
Next.js is vulnerable to RCE in React flight protocol
Next.js Affected by Cache Key Confusion for Image Optimization API Routes
Next.js Content Injection Vulnerability for Image Optimization
Next.js Improper Middleware Redirect Handling Leads to SSRF
Next.JS vulnerability can lead to DoS via cache poisoning
Next.js has a Cache poisoning vulnerability due to omission of the Vary header
Information exposure in Next.js dev server due to lack of origin verification
Next.js Race Condition to Cache Poisoning
Next.js may leak x-middleware-subrequest-id to external hosts
Authorization Bypass in Next.js Middleware
Next.js Allows a Denial of Service (DoS) with Server Actions
Next.js authorization bypass vulnerability
Denial of Service condition in Next.js image optimization
Next.js Cache Poisoning
Next.js Denial of Service (DoS) condition
Next.js Server-Side Request Forgery in Server Actions
Next.js Vulnerable to HTTP Request Smuggling
Next.js missing cache-control header may lead to CDN caching empty reply
Unexpected server crash in Next.js
Improper CSP in Image Optimization API for Next.js versions between 10.0.0 and 12.1.0
Denial of Service Vulnerability in next.js
Unexpected server crash in Next.js.
XSS in Image Optimization API for Next.js
Open Redirect in Next.js
Open Redirect in Next.js versions
Remote Code Execution in next
Directory Traversal in Next.js
Next.js has cross site scripting (XSS) vulnerability via the 404 or 500 /_error page
Directory traversal vulnerability in Next.js
Next.js Directory Traversal Vulnerability