CVE-2026-34749: Payload Payload Has A CSRF Protection Vulnerability

MODERATE
Advisory Identifier: GHSA-p6mr-xf3r-ghq4
CVSS 5.4
CWE-352
Published
Advisory Summary

CVE-2026-34749 is a MODERATE (CVSS 5.4) payload has a csrf protection vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Payload libraries in the npm ecosystem. The issue involves payload has a csrf protection bypass in authentication flow. Remediation is available by upgrading affected packages to version 3.79.1.

CVE-2026-34749 at a Glance

CVE Identifier CVE-2026-34749
GHSA Identifier GHSA-p6mr-xf3r-ghq4
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Payload
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-34749

To remediate this vulnerability, upgrade all affected Payload dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

payload fixed: 3.79.1
npm install payload@3.79.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls payload

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-34749, inspect your project dependencies using npm:

npm ls payload

Analyze the terminal output to locate any version of Payload in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.79.1), your application is affected.

Note: The npm ls payload command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where 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. In Payload, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact A Cross-Site Request Forgery (CSRF) vulnerability existed in the authentication flow. Under certain conditions, the configured CSRF protection could be bypassed, allowing cross-site requests to be made. Consumers are affected if ALL of these are true: - Payload version **< v3.79.1** - `serverURL` is configured ### Patches This vulnerability has been patched in **v3.79.1**. Additional validation has been added to the authentication flow. Consumers should upgrade to **v3.79.1** or later. ### Workarounds There is no complete workaround without upgrading. If consumers cannot upgrade immediately, setting `cookies.sameSite` to `'Strict'` will prevent the session cookie from being sent cross-site. However, this will also require users to re-authenticate when navigating to the application from external links (e.g. email, other sites).

CVE-2026-34749 Affected Payload Versions

1 component(s)
Fixed Versions:
3.79.1
Product / Package Ecosystem Affected Versions Fixed Version
payload
npm
< 3.79.1
3.79.1

References

Frequently Asked Questions

What is CVE-2026-34749?
CVE-2026-34749 is a security vulnerability in Payload involving Payload has a CSRF Protection Bypass in Authentication Flow under CWE-352: Cross-Site Request Forgery (CSRF).
Which Payload versions are affected?
Affected versions include releases prior to 3.79.1 across affected packages: payload.
What version fixes CVE-2026-34749?
Upgrading to 3.79.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is payload affected?
Yes, payload is affected in releases prior to 3.79.1. Upgrade your dependency to 3.79.1 or later.
What is the CVSS score of CVE-2026-34749?
CVE-2026-34749 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L.
What CWE is associated with CVE-2026-34749?
CVE-2026-34749 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (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.).
How can I check npm dependencies for CVE-2026-34749?
Run the dependency tree command: 'npm ls payload'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-p6mr-xf3r-ghq4",
  "modified" : "2026-04-01T21:36:06Z",
  "published" : "2026-04-01T21:36:06Z",
  "aliases" : [ "CVE-2026-34749" ],
  "summary" : "Payload has a CSRF Protection Bypass in Authentication Flow",
  "details" : "### Impact\n\nA Cross-Site Request Forgery (CSRF) vulnerability existed in the authentication flow. Under certain conditions, the configured CSRF protection could be bypassed, allowing cross-site requests to be made.\n\nConsumers are affected if ALL of these are true:\n\n- Payload version **< v3.79.1**\n- `serverURL` is configured\n\n### Patches\n\nThis vulnerability has been patched in **v3.79.1**. Additional validation has been added to the authentication flow.\n\nConsumers should upgrade to **v3.79.1** or later.\n\n### Workarounds\n\nThere is no complete workaround without upgrading. \n\nIf consumers cannot upgrade immediately, setting `cookies.sameSite` to `'Strict'` will prevent the session cookie from being sent cross-site. However, this will also require users to re-authenticate when navigating to the application from external links (e.g. email, other sites).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "payload"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.79.1"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/payloadcms/payload/security/advisories/GHSA-p6mr-xf3r-ghq4"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34749"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/payloadcms/payload"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/payloadcms/payload/releases/tag/v3.79.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-01T21:36:06Z",
    "nvd_published_at" : "2026-04-01T20:16:27Z"
  }
}