<?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://cve.radiocsirt.org</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>Wed, 07 Oct 2026 11:51:21 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-317422</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-317422</link>
      <description>EUVD-2026-317422</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-317422</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42190</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42190</link>
      <description>&lt;p&gt;RedwoodSDK is a server-first React framework. From version 1.0.0-beta.50 to before version 1.2.3, server actions in rwsdk apply HTTP method enforcement but no origin validation. A request originating from a different origin that the browser treats as same-site can invoke a server action with the victim&amp;#39;s session cookie attached. This issue has been patched in version 1.2.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;RedwoodSDK is a server-first React framework. From version 1.0.0-beta.50 to before version 1.2.3, server actions in rwsdk apply HTTP method enforcement but no origin validation. A request originating from a different origin that the browser treats as same-site can invoke a server action with the victim&amp;#39;s session cookie attached. This issue has been patched in version 1.2.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42190</guid>
    </item>
    <item>
      <title>GHSA-m2m6-cff5-3w7c — RedwoodSDK has Same-site CSRF through lack of origin validation in its server actions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m2m6-cff5-3w7c</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: rwsdk&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Server actions in `rwsdk` apply HTTP method enforcement but no origin validation. A request originating from a different origin that the browser treats as same-site can invoke a server action with the victim&amp;#39;s session cookie attached.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker who controls any origin the browser considers same-site with the deployed app can induce an authenticated victim&amp;#39;s browser to invoke arbitrary server actions. The exposure depends on deployment shape:&lt;/p&gt;
&lt;p&gt;- Apps deployed on custom domains (for example `app.example.com`) are exposed whenever the attacker controls any sibling subdomain under the same registrable domain. Plausible vectors include subdomain takeover of stale DNS records pointing at third-party services, cross-site scripting on a sibling application, or content served from a user-content subdomain.
- Apps deployed on platform-suffix domains on the Public Suffix List (`*.workers.dev`, `*.pages.dev`) are not exposed to the sibling-subdomain vector, because sibling subdomains under those suffixes are treated as cross-site.
- In local development, `localhost` on any other port is treated as same-site with the app&amp;#39;s dev server. A separate process running on the developer&amp;#39;s machine can invoke server actions against the dev server.&lt;/p&gt;
&lt;p&gt;The attacker cannot read action responses (`mode: &amp;#34;no-cors&amp;#34;` yields opaque responses). Impact is therefore limited to side effects of action invocation: writes, state changes, and any externally observable action the applicati…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: rwsdk&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Server actions in `rwsdk` apply HTTP method enforcement but no origin validation. A request originating from a different origin that the browser treats as same-site can invoke a server action with the victim&amp;#39;s session cookie attached.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;An attacker who controls any origin the browser considers same-site with the deployed app can induce an authenticated victim&amp;#39;s browser to invoke arbitrary server actions. The exposure depends on deployment shape:&lt;/p&gt;
&lt;p&gt;- Apps deployed on custom domains (for example `app.example.com`) are exposed whenever the attacker controls any sibling subdomain under the same registrable domain. Plausible vectors include subdomain takeover of stale DNS records pointing at third-party services, cross-site scripting on a sibling application, or content served from a user-content subdomain.
- Apps deployed on platform-suffix domains on the Public Suffix List (`*.workers.dev`, `*.pages.dev`) are not exposed to the sibling-subdomain vector, because sibling subdomains under those suffixes are treated as cross-site.
- In local development, `localhost` on any other port is treated as same-site with the app&amp;#39;s dev server. A separate process running on the developer&amp;#39;s machine can invoke server actions against the dev server.&lt;/p&gt;
&lt;p&gt;The attacker cannot read action responses (`mode: &amp;#34;no-cors&amp;#34;` yields opaque responses). Impact is therefore limited to side effects of action invocation: writes, state changes, and any externally observable action the applicati…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m2m6-cff5-3w7c</guid>
    </item>
  </channel>
</rss>
