<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 10:30:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-43864 — React Router allows a DoS via cache poisoning by forcing SPA mode</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-43864</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; remix-run react-router&lt;/p&gt;
&lt;p&gt;React Router is a router for React. Starting in version 7.2.0 and prior to version 7.5.2, it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application. This issue has been patched in version 7.5.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; remix-run react-router&lt;/p&gt;
&lt;p&gt;React Router is a router for React. Starting in version 7.2.0 and prior to version 7.5.2, it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application. This issue has been patched in version 7.5.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-43864</guid>
    </item>
    <item>
      <title>GHSA-f46r-rw29-r322 — React Router allows a DoS via cache poisoning by forcing SPA mode</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-f46r-rw29-r322</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: react-router&lt;/p&gt;
&lt;p&gt;## Summary
After some research, it turns out that it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application.&lt;/p&gt;
&lt;p&gt;## Details
The vulnerable header is `X-React-Router-SPA-Mode`; adding it to a request sent to a page/endpoint using a loader throws an error. Here is [the vulnerable code](https://github.com/remix-run/react-router/blob/e6c53a0130559b4a9bd47f9cf76ea5b08a69868a/packages/react-router/lib/server-runtime/server.ts#L407) :&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;672&amp;#34; alt=&amp;#34;Capture d’écran 2025-04-07 à 08 28 20&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/0a0e9c41-70fd-4dba-9061-892dd6797291&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;To use the header, React-router must be used in Framework mode, and for the attack to be possible the target page must use a loader.&lt;/p&gt;
&lt;p&gt;## Steps to reproduce 
Versions used for our PoC: 
- &amp;#34;@react-router/node&amp;#34;: &amp;#34;^7.5.0&amp;#34;,
- &amp;#34;@react-router/serve&amp;#34;: &amp;#34;^7.5.0&amp;#34;,
- &amp;#34;react&amp;#34;: &amp;#34;^19.0.0&amp;#34;
- &amp;#34;react-dom&amp;#34;: &amp;#34;^19.0.0&amp;#34;
- &amp;#34;react-router&amp;#34;: &amp;#34;^7.5.0&amp;#34;&lt;/p&gt;
&lt;p&gt;1. Install React-Router with its default configuration in Framework mode (https://reactrouter.com/start/framework/installation)
2. Add a simple page using a loader (example: `routes/ssr`)&lt;/p&gt;
&lt;p&gt;![image](https://github.com/user-attachments/assets/d7d04e86-c549…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: react-router&lt;/p&gt;
&lt;p&gt;## Summary
After some research, it turns out that it is possible to force an application to switch to SPA mode by adding a header to the request. If the application uses SSR and is forced to switch to SPA, this causes an error that completely corrupts the page. If a cache system is in place, this allows the response containing the error to be cached, resulting in a cache poisoning that strongly impacts the availability of the application.&lt;/p&gt;
&lt;p&gt;## Details
The vulnerable header is `X-React-Router-SPA-Mode`; adding it to a request sent to a page/endpoint using a loader throws an error. Here is [the vulnerable code](https://github.com/remix-run/react-router/blob/e6c53a0130559b4a9bd47f9cf76ea5b08a69868a/packages/react-router/lib/server-runtime/server.ts#L407) :&lt;/p&gt;
&lt;p&gt;&amp;lt;img width=&amp;#34;672&amp;#34; alt=&amp;#34;Capture d’écran 2025-04-07 à 08 28 20&amp;#34; src=&amp;#34;https://github.com/user-attachments/assets/0a0e9c41-70fd-4dba-9061-892dd6797291&amp;#34; /&amp;gt;&lt;/p&gt;
&lt;p&gt;To use the header, React-router must be used in Framework mode, and for the attack to be possible the target page must use a loader.&lt;/p&gt;
&lt;p&gt;## Steps to reproduce 
Versions used for our PoC: 
- &amp;#34;@react-router/node&amp;#34;: &amp;#34;^7.5.0&amp;#34;,
- &amp;#34;@react-router/serve&amp;#34;: &amp;#34;^7.5.0&amp;#34;,
- &amp;#34;react&amp;#34;: &amp;#34;^19.0.0&amp;#34;
- &amp;#34;react-dom&amp;#34;: &amp;#34;^19.0.0&amp;#34;
- &amp;#34;react-router&amp;#34;: &amp;#34;^7.5.0&amp;#34;&lt;/p&gt;
&lt;p&gt;1. Install React-Router with its default configuration in Framework mode (https://reactrouter.com/start/framework/installation)
2. Add a simple page using a loader (example: `routes/ssr`)&lt;/p&gt;
&lt;p&gt;![image](https://github.com/user-attachments/assets/d7d04e86-c549…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-f46r-rw29-r322</guid>
    </item>
  </channel>
</rss>
