CVE-2026-42190
Received Received - Intake
Server Action Origin Validation Bypass in RedwoodSDK

Publication date: 2026-05-08

Last updated on: 2026-05-08

Assigner: GitHub, Inc.

Description
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's session cookie attached. This issue has been patched in version 1.2.3.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-08
Last Modified
2026-05-08
Generated
2026-05-09
AI Q&A
2026-05-08
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
redwoodjs redwood_sdk From 1.0.0-beta.50 (inc) to 1.2.3 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-352 The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?

The vulnerability has been patched in RedwoodSDK version 1.2.3. The immediate step to mitigate this vulnerability is to upgrade your RedwoodSDK installation to version 1.2.3 or later.


Can you explain this vulnerability to me?

This vulnerability exists in RedwoodSDK, a server-first React framework, in versions from 1.0.0-beta.50 up to but not including 1.2.3. The issue is that server actions enforce HTTP methods but do not validate the origin of requests. As a result, a request coming from a different origin that the browser considers same-site can trigger a server action with the victim's session cookie attached.

This means an attacker could potentially perform actions on behalf of a user by exploiting the lack of origin validation, even though the HTTP method enforcement is in place.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

CVE-2026-42190 is a Same-site Cross-Site Request Forgery (CSRF) vulnerability that allows attackers controlling a same-site origin to invoke arbitrary server actions with the victim's session cookie. This can lead to unauthorized state changes or writes in affected applications.

While the vulnerability does not result in confidentiality or availability loss, the integrity impact is high. This could potentially affect compliance with standards like GDPR or HIPAA, which require protection against unauthorized actions and maintaining data integrity.

Applications handling sensitive personal or health data could be at risk of unauthorized modifications due to this vulnerability, which may lead to non-compliance with regulations that mandate strict access controls and data protection.

The issue has been patched in version 1.2.3 by adding origin validation, which helps mitigate the risk and supports compliance efforts by preventing unauthorized cross-origin requests.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves server actions in RedwoodSDK versions 1.0.0-beta.50 to before 1.2.3 that enforce HTTP methods but lack origin validation, allowing same-site CSRF attacks. Detection involves identifying requests invoking server actions from origins other than the expected one, especially non-GET requests without proper origin headers.

To detect potential exploitation attempts on your network or system, you can monitor HTTP requests to your RedwoodSDK server actions for suspicious origins or missing/incorrect Origin or Referer headers.

Example commands to help detect such activity include:

  • Using tcpdump or tshark to capture HTTP traffic and filter for server action endpoints and non-GET methods:
  • tcpdump -i any -A -s 0 'tcp port 80 or tcp port 443' | grep -i 'POST\|PUT\|DELETE'
  • Using curl or similar tools to test server action endpoints and verify if origin validation is enforced:
  • curl -X POST https://your-redwood-app.com/server-action-endpoint -H 'Origin: https://malicious.example.com' -b 'session=your_session_cookie' -v
  • Checking server logs for requests to server actions with unexpected Origin or Referer headers.

Note that the vulnerability was patched in version 1.2.3 by adding origin/host matching for non-GET requests, so upgrading is the recommended mitigation.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized actions being performed on behalf of a user without their consent, as an attacker can exploit the missing origin validation to send requests that include the victim's session cookie.

This can result in integrity issues where an attacker can manipulate or change data or perform actions that the user did not intend, potentially compromising the security of the application.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart