dbcve.org
RedwoodsdkApplication · Redwoodjs

CVE-2026-39371

HIGH · 8.1 CVSS v3.1 Published 2026-04-07
Fix available
A fix is available. Upgrade to 1.0.6 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RedwoodSDK versions 1.0.0-beta.50 through 1.0.5 improperly allow server functions exported from 'use server' files to be invoked via GET requests instead of only POST. This bypasses intended HTTP method restrictions and enables cross-site GET navigation attacks in cookie-authenticated applications, as browsers automatically send SameSite=Lax cookies on top-level GET requests, allowing attackers to trigger state-changing server functions.

MitigationUpgrade RedwoodSDK to version 1.0.6 or later to obtain the fix that enforces proper HTTP method restrictions on server functions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RedwoodsdkApplication
Affected:>= 1.0.1, < 1.0.6= 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if RedwoodSDK is used in the project
    Check package.json for dependencies containing 'redwoodjs' or '@redwoodjs', or inspect node_modules for @redwoodjs/api package directory
    Affected if The project depends on @redwoodjs/api or similar RedwoodJS packages and the version falls within the affected range (1.0.0, or >=1.0.1 and <1.0.6)
  2. Determine the installed RedwoodSDK version
    Run 'npm list @redwoodjs/api' or check the version field in node_modules/@redwoodjs/api/package.json
    Affected if The installed version is 1.0.0, or >=1.0.1 and less than 1.0.6
  3. Locate use server function files in the project
    Search the codebase for files containing 'use server' directives, typically in the api side of a Redwood project under the 'functions' directory or similar server-side modules
    Affected if The project contains 'use server' files and the RedwoodSDK version is in the affected range
  4. Verify cookie-based authentication is in use
    Inspect the application for session/cookie configuration - check for session setup in api/src/lib/auth.* files or similar session management code that uses browser cookies for authentication
    Affected if The application uses cookie-based authentication (SameSite=Lax cookies) alongside 'use server' functions and the SDK version is vulnerable

A user is affected if they have RedwoodSDK version 1.0.0 or >=1.0.1 but <1.0.6, use 'use server' functions in their application, and rely on cookie-based authentication where GET requests could trigger server functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.6 or later
Fixed in 1.0.6
Interim mitigation

Upgrade RedwoodSDK to version 1.0.6 or later to obtain the fix that enforces proper HTTP method restrictions on server functions.

Recommended fix High confidence

1.0.6

  1. Check the current version of RedwoodSDK (or @redwoodjs/api-server) in your package.json or package-lock.json file
  2. Update the version to 1.0.6 in your package.json
  3. Run 'npm install' or 'yarn install' to update the dependency to the fixed version
  4. Verify the update was successful by checking the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Redwoodsdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39371 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-39371 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data