Advisories
Flaws in things people run, newest first. The level comes from evidence, never from how alarming it sounds.
- For your digestnext: Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
Fix: next 16.4.5
CVE-2026-119351 ·
- For your digestnext: Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
Fix: next 16.4.5
CVE-2026-119790 ·
- For your digestnext: Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays
Fix: next 16.4.1
GHSA-673q-mjm6-r5xr ·
- For your digestnext: Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used
Fix: next 16.4.1 / 15.5.28
GHSA-2464-fhr4-w9xw ·
Fix: next 16.4.1 / 15.5.28
CVE-2026-94482 ·
- For your digestnext: Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service
Fix: next 16.3.8 / 15.5.27
CVE-2026-94484 ·
- For your digestnext: Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass
Fix: next 16.3.8
CVE-2026-94485 ·
Fix: next 16.3.8
CVE-2026-94483 ·
Fix: next 16.3.8 / 15.5.27
CVE-2026-94543 ·
- For your digestnext: Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages
Fix: next 16.3.8
CVE-2026-94544 ·
- For your digestnext: Next.js has information disclosure in development server's Model Context Protocol endpoint
Fix: next 16.3.8
CVE-2026-94486 ·
Fix: next 16.3.8
CVE-2026-103004 ·
Fix: next 16.3.6
GHSA-vcvr-r3jv-pc5j ·
- For your digestnext: Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used
Fix: next 16.3.3 / 15.5.24
GHSA-2xp9-vwfh-vxw4 ·
Fix: next 16.3.3 / 15.5.24
CVE-2026-75604 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64649 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64648 ·
- For your digestnext: Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequences
Fix: next 16.2.11 / 15.5.21
CVE-2026-64647 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64646 ·
- For your digestnext: Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostname
Fix: next 16.2.11 / 15.5.21
CVE-2026-64645 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64644 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64643 ·
- For your digestnext: Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single locale
Fix: next 16.2.11
CVE-2026-64642 ·
Fix: next 16.2.11 / 15.5.21
CVE-2026-64641 ·
- For your digestnext: Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Up
Fix: next 16.2.6 / 15.5.18
CVE-2026-45109 ·
Fix: next 16.2.5 / 15.5.16
CVE-2026-44572 ·
- For your digestnext: Next.js vulnerable to cross-site scripting in App Router applications using CSP nonces
Fix: next 16.2.5 / 15.5.16
CVE-2026-44581 ·
- For your digestnext: Next.js vulnerable to cache poisoning via collisions in React Server Component cache-busting
Fix: next 16.2.5 / 15.5.16
CVE-2026-44582 ·
- For your digestnext: Next.js has cross-site scripting in beforeInteractive scripts with untrusted input
Fix: next 16.2.5 / 15.5.16
CVE-2026-44580 ·
- For your digestnext: Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Components
Fix: next 16.2.5 / 15.5.16
CVE-2026-44579 ·
Fix: next 16.2.5 / 15.5.16
CVE-2026-44577 ·
- For your digestnext: Next.js vulnerable to server-side request forgery in applications using WebSocket upgrades
Fix: next 16.2.5 / 15.5.16
CVE-2026-44578 ·
Fix: next 16.2.5 / 15.5.16
CVE-2026-44576 ·
- For your digestnext: Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes
Fix: next 16.2.5 / 15.5.16
CVE-2026-44575 ·
- For your digestnext: Next.js has a Middleware / Proxy bypass through dynamic route parameter injection
Fix: next 16.2.5 / 15.5.16
CVE-2026-44574 ·
- For your digestnext: Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n
Fix: next 16.2.5 / 15.5.16
CVE-2026-44573 ·
Fix: next 16.2.5 / 15.5.16
GHSA-8h8q-6873-q5fj ·
- For your digestnext: Next.js has a Denial of Service with Server Components
Fix: next 16.2.3 / 15.5.15
GHSA-q4gf-8mx6-v5v3 ·
- For your digestnext: Next.js: HTTP request smuggling in rewrites
Fix: next 16.1.7 / 15.5.13
CVE-2026-29057 ·
Fix: next 16.1.7 / 15.5.14
CVE-2026-27980 ·
Fix: next 16.1.7
CVE-2026-27979 ·
Fix: next 16.1.7
CVE-2026-27978 ·
Fix: next 16.1.7
CVE-2026-27977 ·
- For your digestnext: Next.js HTTP request deserialization can lead to DoS when using insecure React Server Components
Fix: next 16.1.5 / 16.0.11 / 15.6.0-canary.61 / 15.5.10
GHSA-h25m-26qc-wcjf ·
Fix: next 16.1.5 / 15.6.0-canary.61
CVE-2025-59472 ·
- For your digestnext: Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configuration
Fix: next 16.1.5 / 15.5.10
CVE-2025-59471 ·
Fix: next 16.1.0-canary.19 / 16.0.10 / 15.6.0-canary.60 / 15.5.9
GHSA-5j59-xgg2-r9c4 ·
- For your digestnext: Next Server Actions Source Code Exposure
Fix: next 16.1.0-canary.17 / 16.0.9 / 15.6.0-canary.59 / 15.5.8
GHSA-w37m-7fhw-fmv9 ·
Fix: next 16.1.0-canary.17 / 16.0.9 / 15.6.0-canary.59 / 15.5.8
GHSA-mwv6-3258-q52c ·
- For your digestnext: Next.js is vulnerable to RCE in React flight protocol
Fix: next 16.0.7 / 15.5.7 / 15.4.8 / 15.3.6
GHSA-9qr9-h5gf-34mp ·
Follow without an account:everything followedact nowthis weekJSONthis product