Cross-Site Request Forgery (CSRF) in rwsdk (CVE-2026-42190)
Summary
Vulnerability in rwsdk (CVE-2026-42190). Data can be tampered with by attackers. Exploitable via rwsdk. Mitigation: upgrade to 1.2.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42190 has been found in rwsdk.
Attackers can target a specific entry point like rwsdk over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.3/10.
What to do: upgrade rwsdk to 1.2.3 or later.
If unsure, ask your IT team or search "rwsdk CVE-2026-42190" on the vendor's site.
CVE-2026-42190 (rwsdk) — CWE-352 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: rwsdk / app.example.com / localhost / evil.com
Patched: 1.2.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
CSRF (CWE-352) exists in rwsdk. Attackers reach the vulnerable code path via rwsdk without authentication.
Check the vendor advisory for the affected versions of rwsdk. Attack surface: rwsdk / app.example.com / localhost / evil.com.
Severity: Medium (CVSS 5.3/10). Data can be tampered with by attackers.
Update to 1.2.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'rwsdk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'rwsdk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
rwsdkを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade rwsdk to 1.2.3ステージング環境で 1.2.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com