Next.js and React patched critical remote code execution on October 14, 2026
Short answer
On October 14, 2026, the Next.js and React teams published critical advisories for unauthenticated remote code execution. Next.js 16.0.0 through 16.4.0 is affected by a Cache Components bug when a use cache function returns multiple typed arrays, fixed in 16.4.1. A separate image-processing bug, which Netlify identifies as CVE-2026-96889, affects Next.js 10.0.0 through 15.5.27 and 16.0.0 through 16.4.0 on glibc Linux, fixed in 15.5.28 and 16.4.1. React Server Components packages through 19.0.8, 19.1.9, 19.2.8, and 19.3.0 are affected in rare cases, fixed in 19.0.9, 19.1.10, 19.2.9, and 19.3.1. Upgrade and redeploy. Do not send an exploit payload.
Last updated · Sekrd Research
- When: advisories published October 14, 2026 by eps1lon (Next.js) and mattcarrollcode (React).
- Next.js Cache Components: GHSA-673q-mjm6-r5xr, critical, CVSS 9.5. Affected next 16.0.0 through 16.4.0. Patched in 16.4.1.
- Image Optimization: GHSA-2464-fhr4-w9xw, critical. Affected next 10.0.0 through 15.5.27 and 16.0.0 through 16.4.0. Patched in 15.5.28 and 16.4.1. Netlify’s changelog calls this CVE-2026-96889.
- Server Actions DoS: GHSA-p3m5-59mp-jv5r, high, CVSS 8.2. Affected next 13.0.0 through 15.5.27 and 16.0.0 through 16.4.0. Same patched releases.
- React Server Components: GHSA-xqc2-xf4c-x3h3, critical, CVSS 9.5. Patched package versions 19.0.9, 19.1.10, 19.2.9, and 19.3.1.
What happened
October 14, 2026 was a framework patch day, not a single bug. Next.js published three advisories. React published one that covers the server-component packages Next.js, and other RSC bundlers, ship. Netlify’s changelog the same day tells customers to upgrade next to 15.5.28 or 16.4.1 and redeploy, including preview deploys that would otherwise keep the old code until they age out.
The scores on the GitHub advisories are CVSS 9.5 for the two critical remote-code bugs in Next.js Cache Components and in React Server Components, and CVSS 8.2 for the Server Actions denial of service. The image advisory is labeled critical and describes possible remote code execution when Next.js runs on glibc-based Linux. It does not print a numeric score in the advisory text we reviewed. Netlify’s changelog is the page that attaches CVE-2026-96889 to GHSA-2464-fhr4-w9xw. The GitHub advisory page itself, as fetched, does not show that CVE id, so this article cites Netlify for the identifier.
Timeline
- October 14, 2026. GHSA-673q-mjm6-r5xr, GHSA-2464-fhr4-w9xw, and GHSA-p3m5-59mp-jv5r published on vercel/next.js. GHSA-xqc2-xf4c-x3h3 published on react/react.
- Same day. Netlify tells customers on its platform to move to next 15.5.28 or 16.4.1. It says the image bug is not exercised by Netlify Image CDN, and that
next/ogImageResponse on Netlify crashes a function rather than running code. - Patched Next.js lines named in the advisories: 15.5.28 and 16.4.1. There is no 16.4.1-equivalent listed for the 10.x through 14.x ranges other than moving to 15.5.28. The image advisory’s affected range starts at 10.0.0.
What each bug actually requires
Cache Components
GHSA-673q-mjm6-r5xr affects the App Router when Cache Components are in use. The advisory says remote code execution needs a use cache function that returns multiple typed arrays. It also says there is no known workaround for applications that have such functions, and that you should upgrade even if your application does not have them. Affected versions are next 16.0.0 through 16.4.0. The patched version is 16.4.1. CVSS vector on the advisory: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:N.
SVG image processing
GHSA-2464-fhr4-w9xw is a memory bug in an upstream library used for Image Optimization. Next.js says it can lead to remote code execution on glibc-based Linux. Affected ranges are next 10.0.0 through 15.5.27, and next above 16.0.0 through 16.4.0. Patched versions are 15.5.28 and 16.4.1. The documented workaround is to make sure the sharp version Next.js uses is 0.35.5 or newer. Fresh installs pick up a fixed sharp. Upgrading Next.js is how the advisory says package managers will supply that fix. This is a different issue from the December 2025 React Server Components bug, CVE-2025-55182.
Server Actions denial of service
GHSA-p3m5-59mp-jv5r says crafted requests to an App Router app that has at least one Server Action can drive CPU use high enough to block further requests in the same process. Pages Router apps, and App Router apps with no Server Actions, are not vulnerable. There is no workaround besides upgrading. The same patched versions apply: 15.5.28 and 16.4.1. CVSS 8.2, vector CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N.
React Server Components, again
GHSA-xqc2-xf4c-x3h3 says crafted payloads against frameworks that support React Server Components can lead to remote code execution, and that this only affects extremely rare cases where responses transport multiple typed arrays and an attacker-controlled value. The vulnerable packages are react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack, at 19.0.0 through 19.0.8, 19.1.0 through 19.1.9, 19.2.0 through 19.2.8, and 19.3.0. Patched versions listed in the version table are 19.0.9, 19.1.10, 19.2.9, and 19.3.1. One sentence of the advisory writes the first fix as 19.0.09. Apps whose React code does not use a server are not affected. Apps that do not use an RSC bundler or plugin are not affected. The React team says to update immediately.
That range is much wider than the four versions in CVE-2025-55182 (19.0.0, 19.1.0, 19.1.1, 19.2.0). A lockfile that was safe against the December 2025 advisory can still sit inside this October range. 19.0.1, the first patch for the older bug, is inside 19.0.0 through 19.0.8.
How to check if your app is exposed
- In the app repo, run
npm ls next react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack. pnpm and yarn have the same question: what version is installed, not what a banner on the homepage says. - If
nextis below 15.5.28 on the 15.x line, or from 16.0.0 through 16.4.0, upgrade to 15.5.28 or 16.4.1 as appropriate and redeploy. The image advisory’s lower bound is 10.0.0, so an older line is in scope for that bug until it is on 15.5.28. - If any react-server-dom-* package is in the ranges above, upgrade to 19.0.9, 19.1.10, 19.2.9, or 19.3.1 or later. Prefer upgrading the framework that vendors those packages, then re-check
npm ls. - Do not send a proof-of-concept request to production. The check is the version. Netlify adds a practical note: public deploy previews keep the old build until they are deleted.
- v0 apps and Cursor apps on Next.js are in this set when the generated project’s lockfile is. Hosting on Vercel or Netlify does not, by itself, answer the version question. Read the lockfile.
How Sekrd helps
A free scan reports an exact pin of react-server-dom-webpack, parcel, or turbopack at 19.0.0, 19.1.0, 19.1.1, or 19.2.0. That is CVE-2025-55182, rule js-rsc-vulnerable-version. It does not flag the wider October 14, 2026 range, and it does not flag a Next.js version. The November scanner update explains that limit on purpose: a version string has to be unambiguous, and the check does not send an exploit. Use npm ls for GHSA-xqc2-xf4c-x3h3 and the three Next.js advisories. Use a free scan for secrets and headers on the deployed URL while you patch. The v0 and Cursor landing pages describe the same Next.js checks: /v0-security-scanner and /cursor-security-scanner.
Related reading
Frequently asked questions
Which Next.js versions fix the October 14, 2026 advisories?
15.5.28 and 16.4.1. Those two releases are the patched versions named for the image bug and the Server Actions denial of service. The Cache Components bug is fixed in 16.4.1 and applies to next 16.0.0 through 16.4.0.
Is GHSA-xqc2-xf4c-x3h3 the same as CVE-2025-55182?
No. CVE-2025-55182, disclosed in December 2025, covers four specific package versions. The October 14, 2026 advisory covers 19.0.0 through 19.0.8, 19.1.0 through 19.1.9, 19.2.0 through 19.2.8, and 19.3.0 of the three react-server-dom packages, and says the vulnerable case is rare.
Does my app have to use use cache to be affected?
The Cache Components advisory says exploitation of that bug needs a use cache function that returns multiple typed arrays, and it still tells every affected application to upgrade, including ones without that function. The image bug and the Server Actions bug have their own conditions.
What is CVE-2026-96889?
Netlify’s October 14, 2026 changelog uses CVE-2026-96889 as the identifier for GHSA-2464-fhr4-w9xw, the Image Optimization SVG bug. The GitHub advisory fetched for this article does not display that CVE id.
Will a Sekrd scan flag every version in the October advisory?
No. The free scan flags only the four CVE-2025-55182 pins. It does not send an exploit and does not infer a Next.js version from the homepage. Check the lockfile for the October ranges.
Sources
Don't ship until you're sekrd
Run a free scan to find the vulnerabilities your AI missed.
Scan Your App Free