Check these three things.
React Server Components prepare part of the interface on a server, using packages whose names start with react-server-dom. Confirm the installed fix, whether an attacker can reach that server, and whether your records show harm.
-
Application owner: confirm the installed server-dom version group and its fixed release. A 19.3.0 install needs 19.3.1. Each other group has its own fix.
What to confirm
- These releases belong to version groups named by their first two numbers. For example, 19.0.8 is in the 19.0 group.
- The CVE description and the GitHub advisory name these packages:
- react-server-dom-webpack
- react-server-dom-parcel
- react-server-dom-turbopack
- The CVE product field says react. A React interface without one of those packages is outside this flaw.
- Each version group has its own fixed release. The vendor recommends updating affected packages immediately.
- The CVE record lists each group as affected from its start version up to but not including the fix.
- The advisory Patches sentence says 19.0.09. Use 19.0.9. The package tables, the CVE record, and release tag v19.0.9 say 19.0.9.
- The advisory says a listed fixed version on any of these lines is a fix. These sources do not require every app to move to 19.3.1.
- These sources do not say which group is most common.
- If no package record is available, the fix status stays unresolved.
- An affected package you deploy needs its group fix even when the rare response case is unconfirmed.
- Record:
- Package name
- Installed version
- Source of that version
- Date checked
-
Application owner: check whether an attacker can reach the vendor's rare response case.
When the risk applies
- The GitHub advisory says this only affects extremely rare cases where both are true:
- Responses transport multiple typed arrays. A typed array is a block of binary data.
- An attacker-controlled value is included.
- An affected package that is in use needs its group fix even when this case is unconfirmed.
- The vendor says the app is not affected when its React code does not use a server.
- The vendor says the app is not affected when it does not use any of these with React Server Components support:
- A framework
- A bundler
- A bundler plugin
- React's Server Components documentation says they can run:
- Once at build time on a CI server
- On each request on a web server
- The documentation says a web server is not required for build-time use.
- The documentation treats that build environment as a server. Build-time use is not, by itself, the vendor's not-affected case.
- The Server Components name does not show that a server is open to the internet.
- The CVE record and the GitHub advisory require:
- No privileges
- No user interaction
- Both sources set attack requirements to present. The advisory text states the rare response case.
- Frontend React use leaves the package question unresolved.
- Records:
- Whether a server-dom package is in the deployed build
- Whether React Server Components support comes from any one of:
- A framework
- A bundler
- A bundler plugin
- Whether React code uses a server
- Whether an attacker can reach that processing
- Source of each record
- Date checked
- The GitHub advisory says this only affects extremely rare cases where both are true:
-
Security owner: review retained records for unauthorized activity and service interruption.
What the records can show
- Unexpected code run by the application
- Unexpected access to data the application can read
- Unexpected changes to application content or records
- Unexpected connections started by the application
- Interruption in application logs or uptime alerts
- Access to another system requires more than a network connection.
- An interruption leaves the break-in question unresolved.
- A gap in the records leaves harm unresolved.
- Shown unauthorized activity needs a response even when this CVE is not established as the cause.
- A missing KEV entry leaves exploitation unknown.
- CISA’s assessment does not establish whether your systems were attacked.
- These sources do not publish an indicator for this CVE.
If an affected server-dom package is in use, update it to that group's fix even when the rare response case is unconfirmed. Review retained records for harm. A completed update leaves the question of earlier harm open.