New React RSC Vulnerabilities Enable DoS and Source Code Exposure
The React team has released fixes for two new types of flaws in React Server Components (RSC) that, if successfully exploited, could result in denial-of-service (DoS) or source code exposure. The team said the issues were found by the security community while attempting to exploit the patches released for CVE-2025-55182 (CVSS score: 10.0), a critical bug in RSC that has since been weaponized in
AI Analysis
Technical Summary
The React team disclosed three new vulnerabilities in React Server Components (RSC), a framework feature enabling server-side rendering and component streaming. The first two vulnerabilities, CVE-2025-55184 and CVE-2025-67779 (both CVSS 7.5), are denial-of-service (DoS) flaws caused by unsafe deserialization of HTTP request payloads sent to Server Function endpoints. This unsafe deserialization triggers infinite loops that hang the server process, effectively denying service and preventing the handling of subsequent HTTP requests. The third vulnerability, CVE-2025-55183 (CVSS 5.3), is an information leak that allows an attacker to retrieve the source code of Server Functions by sending specially crafted HTTP requests. This leak requires the presence of Server Functions that expose arguments converted into string format, which may not be present in all deployments. These vulnerabilities affect multiple versions of react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack ranging from 19.0.0 to 19.2.2, with patches released in versions 19.0.3, 19.1.4, and 19.2.3. The issues were discovered during attempts to exploit an earlier critical vulnerability, CVE-2025-55182 (CVSS 10.0), which has been weaponized in the wild. The React team credits security researchers RyotaK, Shinsaku Nomura, and Andrew MacPherson for reporting these flaws. The vulnerabilities allow unauthenticated attackers to disrupt service or gain unauthorized access to source code, posing significant risks to confidentiality and availability. The React team emphasizes the importance of rapid patching and notes that additional disclosures reflect a healthy security response cycle. No known exploits are currently active for these new vulnerabilities, but active exploration of the prior critical bug increases urgency for remediation.
Potential Impact
For European organizations, these vulnerabilities pose significant risks. The DoS flaws can disrupt critical web services by causing server processes to hang indefinitely, leading to downtime and degraded user experience. This is particularly impactful for sectors relying on high availability such as e-commerce, finance, healthcare, and public services. The information disclosure vulnerability threatens intellectual property and sensitive business logic confidentiality by exposing source code, which could facilitate further attacks or competitive disadvantage. Organizations using affected React Server Component versions in production environments are vulnerable to unauthenticated remote attacks, increasing the attack surface. Given React's widespread adoption in Europe, especially in technology-driven economies, the potential for service disruption and data leakage is substantial. The vulnerabilities could also undermine customer trust and lead to regulatory compliance issues under GDPR if sensitive data exposure occurs. The absence of known exploits currently provides a window for mitigation, but the weaponization of the related CVE-2025-55182 suggests attackers may soon target these new flaws.
Mitigation Recommendations
European organizations should immediately update all affected React Server Component packages to the patched versions 19.0.3, 19.1.4, or 19.2.3 depending on their deployment. Beyond patching, developers should audit Server Functions to ensure no arguments are implicitly or explicitly converted to string formats that could be exploited for source code disclosure. Implement strict input validation and sanitization on all HTTP request payloads to prevent unsafe deserialization. Employ runtime monitoring and anomaly detection to identify unusual request patterns indicative of exploitation attempts, such as repeated requests triggering infinite loops. Use rate limiting and web application firewalls (WAFs) to mitigate potential DoS attacks. Conduct thorough security testing and code reviews focusing on deserialization logic and Server Function exposure. Maintain an incident response plan tailored to web application DoS and information disclosure scenarios. Finally, keep abreast of React security advisories and community reports to respond swiftly to emerging threats related to RSC.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Italy, Spain
New React RSC Vulnerabilities Enable DoS and Source Code Exposure
Description
The React team has released fixes for two new types of flaws in React Server Components (RSC) that, if successfully exploited, could result in denial-of-service (DoS) or source code exposure. The team said the issues were found by the security community while attempting to exploit the patches released for CVE-2025-55182 (CVSS score: 10.0), a critical bug in RSC that has since been weaponized in
AI-Powered Analysis
Technical Analysis
The React team disclosed three new vulnerabilities in React Server Components (RSC), a framework feature enabling server-side rendering and component streaming. The first two vulnerabilities, CVE-2025-55184 and CVE-2025-67779 (both CVSS 7.5), are denial-of-service (DoS) flaws caused by unsafe deserialization of HTTP request payloads sent to Server Function endpoints. This unsafe deserialization triggers infinite loops that hang the server process, effectively denying service and preventing the handling of subsequent HTTP requests. The third vulnerability, CVE-2025-55183 (CVSS 5.3), is an information leak that allows an attacker to retrieve the source code of Server Functions by sending specially crafted HTTP requests. This leak requires the presence of Server Functions that expose arguments converted into string format, which may not be present in all deployments. These vulnerabilities affect multiple versions of react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack ranging from 19.0.0 to 19.2.2, with patches released in versions 19.0.3, 19.1.4, and 19.2.3. The issues were discovered during attempts to exploit an earlier critical vulnerability, CVE-2025-55182 (CVSS 10.0), which has been weaponized in the wild. The React team credits security researchers RyotaK, Shinsaku Nomura, and Andrew MacPherson for reporting these flaws. The vulnerabilities allow unauthenticated attackers to disrupt service or gain unauthorized access to source code, posing significant risks to confidentiality and availability. The React team emphasizes the importance of rapid patching and notes that additional disclosures reflect a healthy security response cycle. No known exploits are currently active for these new vulnerabilities, but active exploration of the prior critical bug increases urgency for remediation.
Potential Impact
For European organizations, these vulnerabilities pose significant risks. The DoS flaws can disrupt critical web services by causing server processes to hang indefinitely, leading to downtime and degraded user experience. This is particularly impactful for sectors relying on high availability such as e-commerce, finance, healthcare, and public services. The information disclosure vulnerability threatens intellectual property and sensitive business logic confidentiality by exposing source code, which could facilitate further attacks or competitive disadvantage. Organizations using affected React Server Component versions in production environments are vulnerable to unauthenticated remote attacks, increasing the attack surface. Given React's widespread adoption in Europe, especially in technology-driven economies, the potential for service disruption and data leakage is substantial. The vulnerabilities could also undermine customer trust and lead to regulatory compliance issues under GDPR if sensitive data exposure occurs. The absence of known exploits currently provides a window for mitigation, but the weaponization of the related CVE-2025-55182 suggests attackers may soon target these new flaws.
Mitigation Recommendations
European organizations should immediately update all affected React Server Component packages to the patched versions 19.0.3, 19.1.4, or 19.2.3 depending on their deployment. Beyond patching, developers should audit Server Functions to ensure no arguments are implicitly or explicitly converted to string formats that could be exploited for source code disclosure. Implement strict input validation and sanitization on all HTTP request payloads to prevent unsafe deserialization. Employ runtime monitoring and anomaly detection to identify unusual request patterns indicative of exploitation attempts, such as repeated requests triggering infinite loops. Use rate limiting and web application firewalls (WAFs) to mitigate potential DoS attacks. Conduct thorough security testing and code reviews focusing on deserialization logic and Server Function exposure. Maintain an incident response plan tailored to web application DoS and information disclosure scenarios. Finally, keep abreast of React security advisories and community reports to respond swiftly to emerging threats related to RSC.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Article Source
- {"url":"https://thehackernews.com/2025/12/new-react-rsc-vulnerabilities-enable.html","fetched":true,"fetchedAt":"2025-12-12T09:44:47.337Z","wordCount":957}
Threat ID: 693be412406b3dd4e0220011
Added to database: 12/12/2025, 9:44:50 AM
Last enriched: 12/12/2025, 9:45:11 AM
Last updated: 12/12/2025, 4:41:56 PM
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
New Advanced Phishing Kits Use AI and MFA Bypass Tactics to Steal Credentials at Scale
MediumNew React RSC Vulnerabilities Enable DoS and Source Code Exposure
HighMicrosoft Bug Bounty Program Expanded to Third-Party Code
CriticalReact2Shell Exploitation Escalates into Large-Scale Global Attacks, Forcing Emergency Mitigation
Critical$320,000 Paid Out at Zeroday.Cloud for Open Source Software Exploits
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.