What happened: one request, no login, code on the server
(RSC) are React components that run on the server and stream their result to the browser[1]. The browser can also call functions marked to run on the server. React calls these Server Functions and Next.js calls them Server Actions[3,17]. Each one is in effect a public HTTP endpoint that anyone on the internet can send data to.
On Dec 3, 2025 the React team disclosed -2025-55182[1]. The flaw is in how three server-side packages, react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack, decode the data sent to those endpoints. One crafted HTTP request could make React run code chosen by the attacker during decoding[1]. That happens before any check in the application's own code, so a login page or permission check never gets a say. The weakness class is , CWE-502[6]. The severity score is the maximum, CVSS 10.0. It is reachable over the network, needs low effort, no account and no action by a user[1,6]. Google also quotes a CVSS 4.0 score of 9.3[8].
An analogy: a restaurant takes written orders through a window, and one cook follows any instruction written on the slip without asking who handed it in. A firewall rule is a guard at the window who looks for suspicious slips. The patch fixes the cook.
Two details make the flaw worse than it sounds. An app does not need to define a single to be vulnerable: supporting RSC at all is enough[1]. And Wiz found that a default create-next-app production build was exploitable with no code changes by the developer[11]. Many site owners never wrote the vulnerable line and never knowingly used the feature.
The private phase was short. Lachlan Davidson reported the bug through the Meta Bug Bounty on Nov 29, 2025. Meta confirmed it on Nov 30, a fix was built on Dec 1 and hosting providers were briefed privately, and the patch and the CVE went public together on Dec 3[1].
You may see two IDs for this one flaw. CVE-2025-55182 is the upstream React record. Next.js first used CVE-2025-66478 to track the impact on its App Router[2]. The Next.js GitHub advisory now lists only CVE-2025-55182[6], Tenable shows CVE-2025-66478 as deprecated[26], and aggregator pages say it was rejected as a duplicate, which we could not confirm against NVD or CVE.org[27]. In practice, a scanner may report either ID, and both mean the same bug. Vendors and researchers call it "React2Shell"[5,7,8,11].
Who is exposed, and who is not
The vulnerable React server packages were versions 19.0, 19.1.0, 19.1.1 and 19.2.0[1]. Several frameworks and tools ship or depend on them: Next.js with the App Router, React Router through its unstable RSC APIs, Waku, Parcel, the Vite RSC plugin and RedwoodSDK[1]. On the Next.js side the original flaw affected 15.x and 16.x, plus 14.3.0-canary.77 and later canary builds, all with the App Router[2]. Vercel describes the same range as 15.0.0 through 16.0.6 plus the 14 canaries after 14.3.0-canary.76[7].
You were not affected by the original flaw if:
- your React runs only in the browser, with no server-side React code[1];
- you use no framework, bundler or plugin that supports RSC[1];
- you run Next.js 13.x, Next.js 14.x stable, the Pages Router or the Edge Runtime[2].
"Not affected" covers that one bug, not everything that came after. Next.js 14.x stable was hit by the denial-of-service bugs disclosed on Dec 11, 2025, fixed in 14.2.35[4]. Pages Router apps escaped those December bugs, but Next.js still recommended an upgrade[4]. For the October 2026 denial-of-service bug, apps on the Pages Router or with no Server Action were not vulnerable[17].
Whether you fall on the safe side depends on the versions your project actually resolves to, and those are not always the ones you remember writing down.
How to check your own project
For a Next.js app, the react line in package.json tells you little, because Next.js bundles its own copy of the RSC code[28,29]. What matters is the version of next and of the three react-server-dom-* packages. The (package-lock.json, pnpm-lock.yaml or yarn.lock) records what was really installed, including copies pulled in by other packages, and the commands below read it.
Run the command for your package manager from the project root:
- npm:
npm ls next react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack --alllists direct and nested copies, andnpm explain <package>shows which dependency brought a package in[24]. - pnpm:
pnpm why next -randpnpm why react-server-dom-webpack -r; the-rflag covers every workspace package in a monorepo[25]. - yarn:
yarn why nextandyarn why react-server-dom-webpack. The yarn documentation was not among the sources checked for this article, so confirm the syntax withyarn why --help.
Compare the output with the versions in the next section. Then check what is actually deployed: a running container keeps the old code until it is rebuilt[28], and forgotten preview and staging deployments can stay vulnerable long after the main site is fixed[7]. A one-page list of every deployment, each with its lockfile and build date, makes this check quick. That list is our suggestion, not a vendor requirement.
Two helpers exist. On Vercel, the dashboard shows a banner for a production deployment that uses a vulnerable next or react-server-dom-* version[7]. Vercel's tool fix-react2shell-next, run as npx fix-react2shell-next --dry-run, reports without changing anything[23]. It scans package.json files for four named packages and skips node_modules and build folders, so it is not a full dependency audit and cannot see nested copies or deployed images[23].
A firewall rule on your host does not change the result of this check. If the check shows a vulnerable version, the code is vulnerable until you update it, whatever Vercel, Cloudflare or AWS block in front of it[1,5,7]. And do not test your production site with public proof-of-concept code: Vercel advises a sandbox with synthetic data[7].
What to update to as of November 2026
The first Next.js fixes of Dec 3, 2025 (for example 15.5.7 and 16.0.7) were superseded on Dec 11 and again later[2,4]. As of the Nov 3, 2026 security release, the current versions are Next.js 16.4.5 for the 16.x line and 15.5.29 for 15.5[18]. Install the one for your line:
- npm:
npm install [email protected]ornpm install [email protected][18]; - pnpm:
pnpm add [email protected]orpnpm add [email protected]; - yarn:
yarn add [email protected]oryarn add [email protected].
The pnpm and yarn commands install the same package versions; then install from the updated lockfile. Next.js states that there is no workaround for the original flaw, only the update[2].
Older lines need a decision. The December 2025 Next.js table sent 13.3 and 14.x to 14.2.35[4]. Our inference is that old lines may no longer receive fixes, so 15.5 or 16.4 is the safer target, but check the Next.js support policy first. One secondary source claims that Next.js 15 reached end of life on Oct 21, 2026[29], while the Next.js November post still calls 15.5.x "Maintenance LTS"[18]. If you are on 14.3.0-canary.77 or a later canary, move to stable next@14 or a fixed 15 or 16 release[2].
If you use RSC without Next.js, update the packages your framework depends on. For Waku, React's advisory gives one npm command that moves react, react-dom, react-server-dom-webpack and waku itself to their latest releases, with similar commands for the Vite RSC plugin, RedwoodSDK (which needs rwsdk>=1.0.0-alpha.0) and the Parcel or Turbopack packages[1]. If you use the react-server-dom-* packages directly, the patched releases to move to, one per line, are 19.0.9, 19.1.10, 19.2.9 and 19.3.1[14].
Then rebuild and redeploy, and confirm that the lockfile actually changed[28]. Take down old preview and staging deployments that still run old versions[28]. Vercel adds that older deployments can stay vulnerable, and recommends Standard Protection on non-production deployments and a review of shareable links[7].
In December many hosts offered a quicker route than all this. The next section explains why it is not enough.
Why a host's firewall rule does not replace the update
Vercel deployed (WAF) rules worldwide before the announcement, added rules on Dec 5 for new attack patterns, and blocks new deployments of vulnerable versions[7]. AWS updated its managed rule set AWSManagedRulesKnownBadInputsRuleSet (version 1.24 or higher) and added Network Firewall rules[5]. Google, Fastly, Akamai and Cloudflare also put rules in front of their customers[2].
These rules buy hours or days, and the vendors themselves say they are not the fix. React calls hosting mitigations temporary and says not to rely on them[1,3]. Vercel says its rules cannot guarantee protection against every variant and that upgrading "remains the only way" to be fully secure[7]. AWS says its rules do not replace patching[5].
The shield can also fail by itself. On Dec 5, 2025, Cloudflare raised a request body buffer from 128 KB to 1 MB to protect customers and then disabled an internal testing tool. The change triggered a bug in its older proxy, and about 28% of its HTTP traffic returned HTTP 500 errors from 08:47 to 09:12 UTC. It was not an attack[12]. In that case the outage came from the defence itself.
One way to hold this in mind: treat a firewall rule as a loan with a due date, and keep the update ticket next to it. A rule that stays in place unnoticed becomes the only thing between a public endpoint and code execution. The deadline is short. Rapid7 urged patching outside the normal cycle[10], and the next sections show why.
After the update: secrets and signs of compromise
Code that runs on your server can read environment variables, files and cloud metadata, and Wiz saw attackers collect exactly those[11]. Updating closes the hole, but it does not remove someone who is already inside or revoke what they copied.
Next.js guidance dated Dec 6, 2025 says that if your app was online and unpatched as of Dec 4, 2025, 1:00 PM PT, you should rotate (replace) the secrets it uses, most critical first[2]. Vercel goes further: assume vulnerable systems may be compromised, and rotate all application secrets after patching and redeploying[7]. In practice that means database credentials, keys, session and signing secrets, cloud credentials reachable from the host, and deploy tokens. That list is our reading of the vendors' advice.
How long rotation takes depends on how secrets are kept. A secret copied into four config files takes four times the work, and a cloud key shared across projects forces you to touch all of them. Keeping each secret in one place, scoped to one job, also limits damage from other bugs. The source code exposure fixed on Dec 11, 2025 leaked only secrets hardcoded in source, not process.env values read at runtime[3].
Signs of compromise reported in the sources include[5,8]:
- unusual POST requests to app endpoints carrying
next-actionorrsc-action-idheaders; - unexpected processes started by the web server;
- unfamiliar files or changed shell startup files;
- outbound
curlorwgetcalls from the web process; - a hidden directory such as
$HOME/.systemd-utils; - a service named "system-update-service", a known disguise for a cryptominer, and backdoors disguised as
vimorpolkitd.
Function timeouts alone do not prove compromise[7]. If a host looks compromised, rebuild it from a clean image rather than cleaning it by hand; that is standard practice and our recommendation, not a vendor quote. AWS suggests opening a support case rather than waiting to be notified[5].
Real attacks began within hours
Amazon's honeypots, servers set up as decoys, saw exploitation attempts within hours of the Dec 3 disclosure. Among the attackers were the China state-nexus groups Earth Lamia and Jackpot Panda. Many clusters shared infrastructure, which makes attribution hard. On Dec 4, one cluster sent 116 requests in about 52 minutes while it debugged its payloads[5]. Many early public proofs of concept were broken or fake[5,10]. Rapid7 confirmed a working one on Dec 4, and the finder published one on Dec 5 together with a Metasploit module[10]. So working exploits were public about a day after the patch.
CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on Dec 5, 2025, with a due date of Dec 26 for US federal agencies. That comes from secondary reporting, since we could not open the CISA page itself[9]. On Dec 12, Google's Threat Intelligence Group reported several clusters. UNC6600 deployed the MINOCAT tunneler, UNC6586 the SNOWLIGHT downloader, UNC6588 the COMPOOD backdoor, and UNC6603 the HISONIC backdoor, aimed at AWS and Alibaba Cloud in Asia Pacific. Google also saw Iran-nexus actors, and XMRig cryptominers from Dec 5[8]. From its own customer data, Wiz reported credential theft, an attempted install of the Sliver attack framework and at least six cryptomining incidents[11]. Rapid7's honeypots received a remote-control payload (MeshAgent) from Dec 8[10]. Unit 42 confirmed over 30 affected organizations, according to The Hacker News[9].
Counts of exposed servers depend on how they were measured. Shadowserver counted 77,664 vulnerable IP addresses on Dec 5, falling to 28,964 by Dec 7, 2025. Censys counted about 2.15 million internet-facing instances that may be affected[9]. These are different measurements, so one does not correct the other.
The vulnerabilities found after the first patch
The fix for itself (React 19.0.1, 19.1.2 and 19.2.1) held[1,3]. But researchers who tried to get around it found other problems in the same decoder[3]. On Dec 11, 2025 React disclosed two denial-of-service bugs, CVE-2025-55184 and CVE-2025-67779 (both CVSS 7.5), and a source code exposure, CVE-2025-55183 (CVSS 5.3). The first denial-of-service fix (19.0.3, 19.1.4, 19.2.3) turned out to be incomplete, and CVE-2025-67779 is the complete fix for CVE-2025-55184[3]. Another denial-of-service bug, CVE-2026-23864, followed on Jan 26, 2026, fixed in 19.0.4, 19.1.5 and 19.2.4[1,3]. The researchers credited include Andrew MacPherson, RyotaK of GMO Flatt Security, Shinsaku Nomura, Mufeed VH, Joachim Viide and Xiangwei Zhang of Tencent YUNDING LAB[3].
The pattern continued through 2026. Denial-of-service fixes came on Apr 8 (CVE-2026-23869), May 6 (CVE-2026-23870) and Jul 21 (CVE-2026-44907), each scored CVSS 7.5[20,21,22], and another on Oct 14, scored 8.2 under CVSS 4.0[19]. The same day React published a second, separate critical remote code execution advisory, GHSA-xqc2-xf4c-x3h3, scored 9.5 under CVSS 4.0. On the 19.0 line it reaches every React server package release up to 19.0.8, on 19.1 every release up to 19.1.9, on 19.2 every release up to 19.2.8, and it also hits 19.3.0. It arises in rare cases where a response carries multiple typed arrays plus a value the attacker controls[14]. Sources show different CVE statements for it, so the GHSA ID is the reliable one to track[13,14].
In Next.js the October flaw is narrower: versions 16.0.0 through 16.4.0, using the App Router with Cache Components, fixed in 16.4.1[15]. The Oct 14 Next.js release (16.4.1 and 15.5.28) also fixed an image optimization flaw and a Server Action denial-of-service bug[17]. The Nov 3 release that produced 16.4.5 and 15.5.29 mostly fixed Cache Components and image bugs rather than decoder problems[18]. The React advisory says nothing about exploitation of the October flaw. A secondary source says React, Vercel and CISA report none, but that public proof-of-concept claims exist; we could not confirm either point[14,28].
Making the next round routine
The record above suggests that this is an ongoing maintenance task rather than a single emergency. Three developments shape it, each with its own conditions.
Monthly windows. Next.js moved to a formal monthly security release process in July 2026, with advance notice: an announcement on Oct 27 preceded the Nov 3 release[30]. A site owner who books a deployment window on each announcement day makes the update a routine event. That works only if the pipeline can build and deploy from the lockfile without manual steps. Out-of-cycle releases still happen: the Oct 14 release was needed because two fixes had been postponed from September by upstream delays[17].
Hosts that refuse vulnerable code. Vercel blocks new deployments of vulnerable versions[7]. Other hosts may copy this; that is speculation. It helps only with new deployments on that host, and does nothing for a server or container that is already running.
More decoder bugs. Given the cadence of React advisories (Jan 26, Apr 8, May 6, Jul 21 and Oct 14, 2026), more findings in the same code are likely[13]. Whether a complex format decoded on a public endpoint can ever be fully hardened is an open question. That is our reading of the pattern, not a claim from any source.
The honest summary: the December bug was exceptionally severe, it was patched quickly, and attackers moved just as quickly. The ongoing risk now comes less from that one flaw and more from assuming that one patch, or one firewall rule, settled the matter. Two questions are worth asking of any project and any tool that claims to protect it. Which version is actually running right now, according to the lockfile and the deployed build? And does this protection remove the vulnerable code, or only stand in front of it?
Short checklist
- Check whether your server runs React Server Components: Next.js App Router, React Router RSC, Waku, Parcel RSC, the Vite RSC plugin, RedwoodSDK or the
react-server-dom-*packages[1]. - Run the check for your package manager (
npm ls ... --all,pnpm why ... -roryarn why) fornextand the threereact-server-dom-*packages, and check the deployed build too. - Update to the current versions: Next.js 16.4.5 or 15.5.29, or React server packages 19.0.9, 19.1.10, 19.2.9 or 19.3.1[14,18].
- Rebuild, redeploy, confirm the lockfile changed, and take down old preview and staging deployments[7,28].
- Treat a host firewall rule as a stopgap, never as the fix[1,7].
- If the site was online and unpatched in December 2025, rotate its secrets, most critical first, and look for the signs of compromise listed above[2,7].
- Follow the monthly Next.js security releases and the React advisories, and update each time[13,30].