Cross-Site Request Forgery (CSRF) in RedwoodSDK (CVE-2026-39371)
Summary
Vulnerability in RedwoodSDK (CVE-2026-39371). Data can be tampered with by attackers. Mitigation: upgrade to 1.0.6 or later.
Original description
The description as published by the source.
RedwoodSDK is a server-first React framework. From 1.0.0-beta.50 to 1.0.5, erver functions exported from "use server" files could be invoked via GET requests, bypassing their intended HTTP method. In cookie-authenticated applications, this allowed cross-site GET navigations to trigger state-changing functions, because browsers send SameSite=Lax cookies on top-level GET requests. This affected all server functions -- both serverAction() handlers and bare exported functions in "use server" files. This vulnerability is fixed in 1.0.6.
Source: NIST National Vulnerability Database NVD
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-39371 has been found in RedwoodSDK.
Data can be tampered with by attackers. CVSS score: 8.1/10.
What to do: upgrade RedwoodSDK to 1.0.6 or later.
If unsure, ask your IT team or search "RedwoodSDK CVE-2026-39371" on the vendor's site.
CVE-2026-39371 (RedwoodSDK) — CWE-352 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.0.6 — 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 RedwoodSDK.
Check the vendor advisory for the affected versions of RedwoodSDK.
Severity: High (CVSS 8.1/10). Data can be tampered with by attackers.
Update to 1.0.6.
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 'RedwoodSDK' . 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 'RedwoodSDK' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
RedwoodSDKを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade RedwoodSDK to 1.0.6ステージング環境で 1.0.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。