Thank You For Reaching Out To Us
We have received your message and will get back to you within 24-48 hours. Have a great day!

Welcome to Haposoft Blog

Explore our blog for fresh insights, expert commentary, and real-world examples of project development that we're eager to share with you.

react-serve-components-vulnerabilities
Dec 12, 2025
15 min read

React Server Components Vulnerabilities And Required Security Fixes

The React team has disclosed additional security vulnerabilities affecting React Server Components, discovered while researchers were testing the effectiveness of last week’s critical patch (React2Shell). While these newly identified issues do not enable Remote Code Execution, they introduce serious risks, including Denial of Service (DoS) attacks and potential source code exposure. Due to their severity, immediate upgrades are strongly recommended. Overview of the Newly Disclosed Vulnerabilities Security researchers identified two new vulnerability classes in the same React Server Components packages affected by CVE-2025-55182. High Severity: Denial of Service (DoS) CVE-2025-55184 CVE-2025-67779 CVSS Score: 7.5 (High) A maliciously crafted HTTP request sent to a Server Function endpoint can trigger an infinite loop during deserialization, causing the server process to hang and consume CPU indefinitely. Notably, even applications that do not explicitly define Server Functions may still be vulnerable if they support React Server Components. This vulnerability enables attackers to: Disrupt service availability Degrade server performance Potentially cause cascading infrastructure impact The React team has confirmed that earlier fixes were incomplete, leaving several patched versions still vulnerable until this latest release. Medium Severity: Source Code Exposure CVE-2025-55183 CVSS Score: 5.3 (Medium) Researchers discovered that certain malformed requests could cause Server Functions to return their own source code when arguments are explicitly or implicitly stringified. This may expose: Hardcoded secrets inside Server Functions Internal logic and implementation details Inlined helper functions, depending on bundler behavior Important clarification: Only source-level secrets may be exposed. Runtime secrets such as process.env.SECRET are not affected. What Is Affected and Who Needs to Take Action The newly disclosed vulnerabilities impact the same React Server Components packages as the previously reported issue, and affect a range of commonly used frameworks and bundlers. Teams should review their dependency tree carefully to determine whether an upgrade is required. Affected Packages and Versions These vulnerabilities affect the same packages and version ranges as the previously disclosed React Server Components issue. Affected packages react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack Vulnerable versions 19.0.0 → 19.0.2 19.1.0 → 19.1.3 19.2.0 → 19.2.2 Fixed Versions (Required Upgrade) The React team has backported fixes to the following versions: 19.0.3 19.1.4 19.2.3 If your project uses any of the affected packages, upgrade immediately to one of the versions above. ⚠️ If you already updated last week, you still need to update again. Versions 19.0.2, 19.1.3, and 19.2.2 are not fully secure. Impacted Frameworks and Bundlers Several popular frameworks and tools depend on or bundle the vulnerable packages, including: Next.js React Router Waku @parcel/rsc @vite/rsc-plugin rwsdk Refer to your framework’s upgrade instructions to ensure the correct patched versions are installed. Who Is Not Affected Apps that do not use a server Apps not using React Server Components Apps not relying on frameworks or bundlers that support RSC React Native Considerations React Native applications that do not use monorepos or react-dom are generally not affected by these vulnerabilities. For React Native projects using a monorepo, only the following packages need to be updated if they are installed: react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack Upgrading these packages does not require updating react or react-dom and will not cause version mismatch issues in React Native. Recommended Solutions and Mitigation Strategy While upgrading to the fixed versions is mandatory, these vulnerabilities also expose broader weaknesses in dependency management and secret handling that teams should address to reduce future risk. Immediate Fix All affected applications should upgrade immediately to one of the patched versions: 19.0.3 19.1.4 19.2.3 Previously released patches were incomplete, and hosting provider mitigations should be considered temporary safeguards only, not a long-term solution. Updating to the fixed versions remains the only reliable mitigation. Automate Dependency Updates to Reduce Exposure Time Modern JavaScript ecosystems make it difficult to manually track security advisories across all dependencies. Using tools such as Renovate or Dependabot helps automatically detect vulnerable versions and create upgrade pull requests as soon as fixes are released. This reduces response time and lowers the risk of running partially patched or outdated packages in production. Ensure CI/CD Pipelines Can Absorb Security Upgrades Safely Frequent dependency upgrades are only safe when supported by reliable automated testing. Maintaining comprehensive CI/CD pipelines with sufficient test coverage allows teams to apply security updates quickly while minimizing the risk of breaking changes. This enables faster remediation when new vulnerabilities are disclosed. Remove Secrets from Source Code to Limit Blast Radius Secrets embedded directly in source code may be exposed if similar vulnerabilities arise again. Store secrets using managed services such as AWS SSM Parameter Store or AWS Secrets Manager Implement key rotation mechanisms without downtime Even if source code is exposed, properly managed runtime secrets significantly limit real-world impact. Why Follow-Up CVEs Are Common After Critical Disclosures It is common for critical vulnerabilities to uncover additional issues once researchers begin probing adjacent code paths. When an initial fix is released, security researchers often attempt to bypass it using variant exploit techniques. This pattern has appeared repeatedly across the industry. A well-known example is Log4Shell, where multiple follow-up CVEs were reported after the first disclosure. While additional disclosures can be frustrating, they usually indicate: Active security review Responsible disclosure A healthy patch and verification cycle Final Notes Some hosting companies set up quick fixes, yet those aren't enough on their own. Keeping dependencies updated is still a top way to stay safe from new supply-chain risks. If your application uses React Server Components, reach out to Haposoft now! We'll figure out what’s impacted while taking care of the update without mess. It means going through your dependencies one by one, making sure everything builds right in the end.
critical-vulnerability-react-server-components
Dec 04, 2025
10 min read

Security Advisory: Critical Vulnerability in React Server Components (CVE-2025-55182)

On December 3, 2025, the React team revealed a critical Remote Code Execution vulnerability in React Server Components (RSC). It affects several RSC packages and some of the most widely used React frameworks, including Next.js. A fix is already out, so the urgent step now is simply checking whether your project uses these packages—and updating to the patched versions if it does. Overview of the Vulnerability A newly reported flaw allows unauthenticated Remote Code Execution (RCE) on servers running React Server Components. Type: Unauthenticated Remote Code Execution CVE: CVE-2025-55182 (NIST , GitHub Advisory Database) Severity: CVSS 10.0 (Maximum severity) This means an attacker could execute arbitrary code on the server without any form of authentication, giving them full control of the affected environment. The issue is caused by a flaw in how React decodes payloads sent to React Server Function endpoints. A maliciously crafted HTTP request can trigger unsafe deserialization, leading to remote code execution. React will publish additional technical details once the patch rollout is fully completed. Scope of Impact Any application that supports React Server Components may be exposed, even if it never defines any Server Function endpoints. The vulnerability exists in the underlying RSC support layer used by multiple frameworks and bundlers. Your application is not vulnerable if: Your React code does not run on a server, or Your application does not use a framework, bundler, or plugin that supports React Server Components. Traditional client-only React applications are unaffected. Affected Versions and Components The vulnerability is tied to specific versions of the React Server Components packages and to the frameworks that depend on them. Identifying whether your project uses any of these versions is the first step in determining your exposure. Vulnerable Packages The issue affects the following packages in versions 19.0, 19.1.0, 19.1.1, and 19.2.0: react-server-dom-webpack react-server-dom-parcel react-server-dom-turbopack Affected Frameworks and Bundlers Several frameworks that rely on these packages are also impacted, including: Next.js React Router (when using unstable RSC APIs) Waku @parcel/rsc @vitejs/plugin-rsc Redwood SDK Security Fix and Recommended Actions The React team has released patched versions, and major frameworks have issued corresponding updates. Applying these fixes promptly is the only reliable way to remove the vulnerability from affected projects. Patched Versions The React team has released fixed versions: 19.0.1 19.1.2 19.2.1 (or any version newer than these) Upgrading to a patched release is mandatory to eliminate the vulnerability. Framework Updates Framework maintainers have also published security updates. For example, Next.js users must upgrade to one of the following patched versions: next@15.0.5 next@15.1.9 next@15.2.6 next@15.3.6 next@15.4.8 next@15.5.7 next@16.0.7 Other ecosystems (React Router, Redwood, Vite plugin, Parcel, Waku, etc.) also require upgrading to their latest patched versions. What Development Teams Should Do Now We recommend the following immediate steps: Audit all projects to confirm whether React Server Components or related frameworks are in use. Check package versions for the affected libraries listed above. Upgrade to the patched versions immediately if your application falls within the impacted scope. Review deployment environments for any unusual activity (optional but advisable for security). Document and report the findings to your internal security or project stakeholders. Conclusion This vulnerability (CVE-2025-55182) is one of the most severe vulnerabilities ever disclosed within the React ecosystem, and it may impact a wide range of modern React-based applications. To maintain security and prevent potential exploitation, all teams should: Review their applications, Identify affected components, and Apply the necessary upgrades without delay. If you need a security audit or patch support within your React-based web development projects, Haposoft is ready to step in.
cta-background

Subscribe to Haposoft's Monthly Newsletter

Get expert insights on digital transformation and event update straight to your inbox

Let’s Talk about Your Next Project. How Can We Help?

+1 
© Haposoft 2025. All rights reserved