React and Next.js Vulnerabilities: Latest CVEs and Version Check

React and Next.js Security in Short

React used to run only in the browser. With React Server Components and Next.js it runs on your server too, so a flaw there can be a server flaw: React2Shell (CVE-2025-55182) let attackers run code on servers through React Server Components and was exploited widely.

Some Next.js advisories are published only on GitHub and npm and never get a CVE, so this page can show fewer than npm audit does. Run that as well.

How to Keep React and Next.js Patched

Update next, react, react-dom and any react-server-dom-* packages together, then rebuild and redeploy. Fixing package.json does nothing until the new build is live.
Run npm audit (or your package manager's equivalent) in CI, so a known flaw blocks a deploy.
If you're on a hosted platform, it may block some attacks, but your app's own copy still needs updating.

The Past Eight Weeks

9 flaws, newest first.

10 Nov 2026 React · Remote code execution React is a JavaScript library for building user interfaces. CVE-2026-126187 9.5

React is a JavaScript library for building user interfaces. From 19.0.0 until 19.0.9, 19.1.10, 19.2.9, and 19.3.1, the react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack packages are vulnerable to unauthenticated remote code execution through crafted payloads targeting frameworks that support React Server Components. The vulnerability only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value. Applications whose React code does not use a server are not affected. Applications that do not use a framework, bundler, or bundler plugin that supports React Server Components are not affected. This issue is fixed in versions 19.0.9, 19.1.10, 19.2.9, and 19.3.1.

Patch now · NVD Record

22 Oct 2026 Next.js · Denial of service Next.js is a React framework for building full-stack web applications. CVE-2026-94482 8.2

Next.js is a React framework for building full-stack web applications. From 13.0.0 until 15.5.28 and 16.4.1, crafted requests targeting App Router applications with at least one Server Action can cause excessive CPU consumption and block processing of further requests in the same process. Applications using the Pages Router and App Router applications without Server Actions are not affected. This issue is fixed in versions 15.5.28 and 16.4.1.

Patch this week · NVD Record

2 Oct 2026 Server-side request forgery Next.js is a React framework for building full-stack web applications. CVE-2026-94483 6.5

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, Image Optimization can follow attacker-controlled DNS resolution for a remote URL that matches images.remotePatterns, allowing the optimized image fetch to reach private IP addresses after the URL passes the allow-list check. Applications without images.remotePatterns are not affected. Administrators unable to upgrade should audit allow-listed hosts and avoid entries whose DNS records are not trusted. This issue is fixed in version 16.3.8.

Keep an eye · NVD Record

2 Oct 2026 Security flaw Next.js is a React framework for building full-stack web applications. CVE-2026-94486 5.4

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the next dev development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

Keep an eye · NVD Record

2 Oct 2026 Security flaw Next.js is a React framework for building full-stack web applications. CVE-2026-94485 5.3

Next.js is a React framework for building full-stack web applications. From 16.0.0 until 16.3.8, the `next dev` development server exposes a Model Context Protocol endpoint without reliably restricting cross-site requests. A malicious website visited by a developer can reach the endpoint and read the project's disk location, source code snippets from error reports, route inventory, and development logs. Production deployments do not serve this endpoint. This issue is fixed in version 16.3.8.

Keep an eye · NVD Record

2 Oct 2026 Security flaw Next.js is a React framework for building full-stack web applications. CVE-2026-94543 5.3

Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, self-hosted applications using the Pages Router with statically generated or Incremental Static Regeneration pages can key a response cache entry without sufficiently binding it to the source route. A request can replace one page's cache entry with content from a different route, causing the affected page to serve incorrect content to every visitor until revalidation. Applications deployed on Vercel are not affected. This issue is fixed in versions 15.5.27 and 16.3.8.

Keep an eye · NVD Record

2 Oct 2026 Security flaw Next.js is a React framework for building full-stack web applications. CVE-2026-94484 4.8

Next.js is a React framework for building full-stack web applications. From 15.0.0 until 15.5.27 and 16.3.8, applications with a root-level catch-all page and statically generated or Incremental Static Regeneration routes can use a shared response cache key that is insufficiently scoped to the source route. A single unauthenticated crafted request can poison that cache, causing cross-user content substitution or persistent denial of service until the poisoned entry is revalidated or replaced. This issue is fixed in versions 15.5.27 and 16.3.8.

Keep an eye · NVD Record

2 Oct 2026 Security flaw Next.js is a React framework for building full-stack web applications. CVE-2026-94544 4.2

Next.js is a React framework for building full-stack web applications. From 16.3.0 until 16.3.8, pending use cache fills for the same key are shared without separating Draft Mode requests from regular requests. An overlapping regular request can receive unauthenticated unpublished content from an editor's Draft Mode fill, while an overlapping Draft Mode request can receive published content from a regular fill. When the regular request prerenders a page, the draft-dependent content can persist in the generated page and be served to later visitors until revalidation. Sites are affected when Cache Components or experimental.useCache is enabled and cached functions return draft-dependent content. This issue is fixed in version 16.3.8.

Keep an eye · NVD Record

1 Oct 2026 Security flaw Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their … CVE-2026-103004 5.3

Next.js versions from 16.3.0 to 16.3.7 warm `use cache` handlers using `next/root-params` and can leak their return value to pages with different root params. With Cache Components enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function that reads a root param can be keyed incorrectly when the inner call is served from an existing entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value — whether the page is prerendered at build time or at runtime, or rendered dynamically. Shared cache headers let downstream caches redistribute the content further. What values are leaked cannot be attacker controlled. Which value's content is served depends only on which invocation wrote the entry first. This has been patched in 16.3.8.

Keep an eye · NVD Record