Skip to content
Brief Security & Trust ·

React fixes server flaw that could let attackers run code without a login

GitHub's advisory calls the trigger rare, but four React 19 releases carry the fix.

In brief
  • GitHub's advisory says crafted payloads can let an attacker run code on servers using React Server Components. Four fixed releases are out.
  • The advisory limits the flaw to extremely rare cases. Apps without server code, or without Server Components support in their tooling, are not affected.

GitHub's Advisory Database said on 10 November that crafted payloads can lead to remote code execution in frameworks that support React Server Components. In plain terms, an attacker could run their own code on the server. The advisory's title says no login is needed. Affected releases are 19.0.0 to 19.0.8, 19.1.0 to 19.1.9, 19.2.0 to 19.2.8, and 19.3.0. Teams on those lines can move to 19.0.9, 19.1.10, 19.2.9 or 19.3.1, which carry the fix.

The advisory says the flaw only affects extremely rare cases. A response must carry several typed arrays, which are blocks of raw numbers, along with a value the attacker controls. Apps are not affected if their React code uses no server. They are also safe if no framework, bundler or bundler plugin they use supports Server Components. The advisory does not say whether anyone has used the flaw in attacks. It gives no count of exposed apps.

Our reading: running the affected code is not the same as meeting the trigger. The advisory limits exploitability to the rare case, so the first task is an inventory. Check whether your tooling supports Server Components and which React version it uses, then upgrade, as the advisory urges. It is also worth asking who owns framework upgrades.

A WebPulse Brief: a short report of an important event, written by the WebPulse Newsroom with AI assistance and checked against the reporting below. When there is more to explain, we follow up with a full story. How we use AI.

Reporting: GitHub Advisory Database.