Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.3amended

RedwoodSDK has Same-site CSRF through lack of origin validation in its server actions

CVE-2026-42190GHSA-m2m6-cff5-3w7c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (rwsdk 1.2.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm rwsdk

    Affected
    >= 1.0.0-beta.50, <= 1.2.2
    Fixed in
    1.2.3

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N
EPSS
  • CVE-2026-42190: 0.11% estimated exploitation activity in the next 30 days; percentile 1.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Impact An attacker who controls any origin the browser considers same-site with the deployed app can induce an authenticated victim's browser to invoke arbitrary server actions. The exposure depends on deployment shape: - 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-m2m6-cff5-3w7c

  2. Revision 1 · created ·

    Published from osv record GHSA-m2m6-cff5-3w7c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-42190

Advisory: RedwoodSDK has Same-site CSRF through lack of origin validation in its server actions
IDs: CVE-2026-42190, GHSA-m2m6-cff5-3w7c
Record: https://patchnext.com/advisories/cve-2026-42190 (revision 2, source checked 26 Oct 2026, 12:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rwsdk 1.2.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm rwsdk: affected >= 1.0.0-beta.50, <= 1.2.2; fixed in 1.2.3

## Suggested inspection (read-only)
- `npm ls rwsdk --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rwsdk.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m2m6-cff5-3w7c (OSV record GHSA-m2m6-cff5-3w7c lists affected ranges: npm rwsdk >=1.0.0-beta.50 <1.2.3 (fixed))
- Verified: https://github.com/advisories/GHSA-m2m6-cff5-3w7c (GitHub-reviewed advisory GHSA-m2m6-cff5-3w7c lists affected ranges: npm rwsdk >=1.0.0-beta.50 <=1.2.2)

Commands are suggestions: review each one before running it.

Loading voting…