← All posts

Next.js vulnerabilities in 2026, up to the November release

Théotime Quéré

Co-founder, CentralCSP ·

Last update:

On 3 November 2026 Vercel shipped Next.js 16.4.5 and 15.5.29, the November security release, with seven fixes: one rated High and six Medium, most of them in Cache Components. It follows an out-of-band update on 14 October (16.4.1 and 15.5.28) that fixed two critical unauthenticated remote code execution (RCE) flaws, and the August release that fixed the AVIF image RCE. If you run Next.js yourself, the version to be on today is 16.4.5 or 15.5.29.

This post covers the November release, the critical RCEs of 2026, who is exposed, the version to run per release line, and every Next.js security release of 2026, with React2Shell from December 2025 at the start because it still drives most "is my Next.js version vulnerable" searches.

Next.js security release, November 3 2026

The November 2026 Security Release ships in 16.4.5 (Active LTS) and 15.5.29 (Maintenance LTS):

npm install next@16.4.5   # 16.4
npm install next@15.5.29  # 15.5

It fixes seven advisories. None is rated Critical, and most need a specific setup to matter:

  • Cross-tenant cache disclosure when combining unstable_cache and use cache (GHSA-mfr8-8qww-v76h, High). With Cache Components, a public use cache function that reads a root parameter such as a tenant id, and is called both directly and inside unstable_cache, can store and serve another tenant's result.
  • Cross-root-parameter disclosure in nested use cache functions (GHSA-vc7v-qv4w-wrv8, Medium). Content generated for one tenant, site or locale can be reused for another.
  • Cross-user cache disclosure and poisoning through binary use cache arguments (GHSA-rhh4-g77r-r9qj, Medium). Distinct binary arguments can produce the same cache identity.
  • Shared shell cache poisoning in self-hosted applications (Medium, no advisory link in the release post). Affects next start with Cache Components and Partial Prefetching off, on a specific dynamic route shape.
  • Cross-client response injection through stale compressed response framing (GHSA-pc58-hwjq-p385, Medium). Self-hosted apps that return a fetched Response unchanged, behind an HTTP/1.1 reverse proxy that queues pipelined requests on a shared connection.
  • Cookie values exposed through an internal response header in Edge routes (GHSA-f3mh-rxg3-f5g2, Medium). Edge route handlers that set cookies with NextResponse.cookies.set() can leak them, HttpOnly included, in the x-middleware-set-cookie header that same-origin JavaScript can read.
  • SVG rejection bypass in Image Optimization (GHSA-7qx7-33qx-rqx2, Medium). An image from an allowed source can be misclassified as AVIF and decoded as SVG despite images.dangerouslyAllowSVG: false.

The release post states the limits of several findings itself: the cookie leak needs attacker-controlled JavaScript already running on the same origin, and the SVG bypass does not by itself demonstrate cross-site scripting or RCE. The cookie leak is a good reason to keep a strict Content Security Policy (CSP) on a Next.js site, since it only matters once injected script runs.

The October and September out-of-band updates

Two updates shipped outside the monthly schedule because an upstream fix could not wait.

On 14 October 2026, 16.4.1 and 15.5.28 fixed two critical unauthenticated RCEs and one High denial of service:

  • GHSA-673q-mjm6-r5xr: RCE in App Router applications with Cache Components when a use cache function returns multiple typed arrays. Vercel lists no workaround and asks everyone to upgrade, even without such functions.
  • CVE-2026-96889 (GHSA-2464-fhr4-w9xw): RCE through an upstream image library when the Image Optimization API handles SVG on glibc-based Linux. The workaround is to make sure Next.js uses sharp 0.35.5 or later.
  • GHSA-p3m5-59mp-jv5r: CPU exhaustion in App Router applications with at least one Server Action.

On 22 September 2026, 16.3.6 fixed GHSA-vcvr-r3jv-pc5j, a critical RCE in the Node.js ImageResponse of next/og caused by an upstream Satori issue. It affects 16.2.0 up to 16.3.5; the Edge ImageResponse and Next.js 15.x are not affected (15.5.26 only adds hardening).

Next.js vulnerability 2026, the AVIF image RCE

The advisory is GHSA-2xp9-vwfh-vxw4, titled "Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are used". It is rated Critical, CVSS 9.5 (CVSS 4.0), and had no CVE id at the time of writing.

The flaw is not in Next.js code. Next.js optimizes images with sharp, sharp decodes AVIF through the libheif library, and libheif has a memory corruption bug tracked upstream as GHSA-g89c-p67h-r497. When Next.js optimizes an attacker-controlled AVIF image, that bug can lead to code execution on the server.

  • Affected: Next.js 10.0.0 up to 15.5.23, and 16.x before 16.3.3.
  • Fixed: 15.5.24 and 16.3.3. The fix disables AVIF optimization until a patched libheif reaches sharp: AVIF images are served as-is, not resized.
  • Exposed: self-hosted applications that enable AVIF. Next.js only optimizes to AVIF when image/avif is in images.formats in next.config.js; the default is ['image/webp']. Applications hosted on Vercel are protected and need no action, according to Vercel.

The release also fixed CVE-2026-75604, a second critical RCE (CVSS 9.0). It is a path traversal in the incremental cache that only works on servers running on a Windows filesystem, in applications that use both the Pages Router and the App Router without Cache Components. It affects 13.4 and later before 15.5.24, and 16.0 before 16.3.3. Linux and macOS are not affected, and Vercel lists no workaround. A public proof of concept has been published on GitHub.

Which Next.js version to run now

Upgrade to the November release, which includes every earlier 2026 fix:

npm install next@16.4.5   # Active LTS
npm install next@15.5.29  # Maintenance LTS
Release lineMinimum for the AVIF and Windows RCEs (August)Minimum for the October RCEsVersion to run today
16.x16.3.316.4.116.4.5
15.x15.5.2415.5.2815.5.29
14.x and olderNo patched releaseNo patched releaseMove to 15.5.29 or 16.4.5

Vercel publishes security fixes for the Active LTS and Maintenance LTS lines. Next.js 16.4 shipped on 6 October 2026, and the October and November fixes were published for 16.4 and 15.5 only, so an application on 16.3 or earlier 16.x should move to 16.4.5. If you are on 15.0 to 15.4, upgrade to 15.5.29. The May 2026 release notes state that every 13.x and 14.x version is affected by that release's advisories.

Am I affected?

Check the version first, then the conditions. A version in the affected range does not prove an application is exploitable; a version outside it rules the advisory out.

For the AVIF RCE (GHSA-2xp9-vwfh-vxw4), you are exposed only if all of these hold:

  • You self-host Next.js (your own server, container, or a host other than Vercel).
  • images.formats in next.config.js contains image/avif.
  • Your version is 10.0.0 to 15.5.23, or a 16.x release before 16.3.3.

For CVE-2026-75604, you are exposed only if all of these hold:

  • The Next.js server runs on Windows.
  • The application uses both the Pages Router and the App Router, without Cache Components.
  • Your version is 13.4 or later and before 15.5.24, or 16.x before 16.3.3.

For the November advisories, check whether you use Cache Components (use cache, unstable_cache), whether you self-host with next start, and whether Edge route handlers set cookies with NextResponse.cookies.set(). Applications that do none of these are outside most of that release.

If you cannot upgrade today, remove image/avif from images.formats so AVIF optimization stops. That closes the AVIF path only. There is no workaround for the Windows flaw or for the October use cache RCE. For the October SVG flaw (CVE-2026-96889), Vercel's workaround is to make sure the sharp version Next.js uses is 0.35.5 or later.

// next.config.js
module.exports = {
  images: {
    formats: ['image/webp'], // was ['image/avif', 'image/webp']
  },
}

Every Next.js security release of 2026

Next.js moved to preannounced security releases in July 2026, so fixes now land in batches on dated releases, with out-of-band updates when an upstream fix cannot wait. The fixed versions below are the ones Vercel published for each batch.

DateAdvisoriesHighest severityImpactFixed in
3 Dec 2025CVE-2025-66478 (React CVE-2025-55182, "React2Shell")Critical, CVSS 10.0Unauthenticated RCE through the React Server Components protocol, App Router only. Exploited in the wild, added to the CISA Known Exploited Vulnerabilities catalog on 5 December 202515.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, 16.0.7
16 Mar 2026CVE-2026-27980Moderate, CVSS 6.9The /_next/image disk cache had no size limit, so requests for many image variants could fill the disk (denial of service), mainly on self-hosted apps15.5.14, 16.1.7
7 May 202613 advisories, including React CVE-2026-23870HighAuthorization and middleware bypasses, SSRF through WebSocket upgrades, denial of service in React Server Components, cache poisoning, XSS15.5.18, 16.2.6
20 Jul 20269 advisories, including CVE-2026-64641, CVE-2026-64642, CVE-2026-64645, CVE-2026-64649HighServer Actions denial of service, middleware bypass with Turbopack and a single locale, SSRF through rewrites and Server Actions15.5.21, 16.2.11
25 Aug 2026GHSA-2xp9-vwfh-vxw4 and CVE-2026-75604CriticalUnauthenticated RCE through AVIF optimization, and on Windows-hosted servers15.5.24, 16.3.3
22 Sep 2026GHSA-vcvr-r3jv-pc5jCriticalRCE in the Node.js ImageResponse (next/og) through an upstream Satori issue, 16.2.0 to 16.3.5 only15.5.26 (hardening), 16.3.6
30 Sep 20267 advisories, including CVE-2026-94483HighSSRF in Image Optimization when images.remotePatterns is set, SSG and ISR cache poisoning, information disclosure15.5.27, 16.3.8
14 Oct 2026GHSA-673q-mjm6-r5xr, CVE-2026-96889 and GHSA-p3m5-59mp-jv5rCriticalUnauthenticated RCE in use cache functions returning typed arrays and in SVG image optimization on glibc Linux, Server Actions denial of service15.5.28, 16.4.1
3 Nov 20267 advisories, including GHSA-mfr8-8qww-v76hHighCross-tenant and cross-user cache disclosure with Cache Components, shell cache poisoning, response injection behind HTTP/1.1 proxies, cookie exposure in Edge routes, SVG rejection bypass15.5.29, 16.4.5

Three patterns stand out. Five of the 2026 batches (March, August, 30 September, 14 October and November) touch the Image Optimization API (/_next/image), which is the part of Next.js that processes untrusted input by design. Cache Components is the new hot spot: the October RCE and four of the seven November advisories involve use cache or its caches. And the self-hosted path carries most of the exposure: several advisories state that Vercel deployments are not affected.

How to check which Next.js version a site runs

On your own project, the answer is in package.json and the lockfile: npm ls next prints the installed version.

From the outside, paste the URL into the free Technology Checker. It lists the technologies the page uses, including Next.js when it can read it, with the version, whether that version is outdated or at end of life, and the known CVEs affecting it, each with the version that fixes it. The checker reads the page, not your server configuration: it cannot see images.formats, your hosting platform, or which router you use. Check the version there, then check the conditions above.

The same check covers the rest of the page, since the CVEs most sites carry come from libraries loaded next to the framework. For the method behind finding those, read How to detect vulnerable JavaScript libraries on a live website; for the manual and tool-based ways to read a site's stack, What technology is this website using, and is any of it outdated.

Get told when the next advisory lands

A one-off check answers for one page on one day, and Next.js has shipped eight security releases and updates in 2026 so far. CentralCSP inventories the scripts your visitors' browsers run on every page, identifies the library and version behind each one, and alerts you when a new CVE affects a version you serve. The inventory is described in Technologies, and the supply-chain feature page has the tour.

Patching the framework is half the work on a Next.js site. The other half is limiting what an injected script could do if one got through, which a strict Content Security Policy (CSP) handles: see How to set up a CSP nonce in Next.js and Google Tag Manager under a strict CSP in Next.js. Start free with CentralCSP to see the versions your pages serve.

FAQ

Is my Next.js version vulnerable?

If you run a version older than 16.4.5 or 15.5.29, at least one 2026 advisory applies to it. Whether it is exploitable depends on the advisory's conditions: the AVIF RCE needs self-hosting and image/avif in images.formats, CVE-2026-75604 needs a Windows server, and most November advisories need Cache Components. Upgrading to 16.4.5 or 15.5.29 covers every advisory listed in this post.

What did the November 3, 2026 Next.js security release fix?

Seven advisories, fixed in 16.4.5 and 15.5.29: one High (cross-tenant cache disclosure when unstable_cache and use cache are combined) and six Medium, covering cache disclosure and poisoning with Cache Components, response injection behind some HTTP/1.1 proxies, cookie exposure in Edge routes, and an SVG check bypass in Image Optimization. None is rated Critical.

Does the AVIF vulnerability affect apps hosted on Vercel?

No. Vercel states that applications hosted on its platform are protected and need no upgrade, configuration change, or redeploy. Self-hosted applications that enable AVIF in images.formats are the ones exposed.

Does GHSA-2xp9-vwfh-vxw4 have a CVE id?

Not at the time of writing. The Next.js advisory lists no CVE, and the root cause is tracked upstream in libheif as GHSA-g89c-p67h-r497. Search for the GHSA id when you look up fixes or scanner findings.

What was React2Shell?

React2Shell is the name given to CVE-2025-55182, a CVSS 10.0 flaw in the React Server Components protocol disclosed on 3 December 2025, tracked in Next.js as CVE-2025-66478. It allowed unauthenticated RCE in App Router applications on Next.js 15.x and 16.x, was exploited in the wild within days, and is fixed in the versions listed in the timeline. Vercel's npx fix-react2shell-next tool updates affected projects.

Is Next.js 14 still supported?

Vercel publishes security fixes for the Active LTS (16.4) and Maintenance LTS (15.5) lines. The May 2026 release notes state that all 13.x and 14.x versions are affected by that release's advisories, so a 14.x application should move to 15.5.29 or 16.4.5.

Sources