dbcve.org
PayloadApplication · Payloadcms

CVE-2026-34750

MEDIUM · 6.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to 3.78.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Payload is a free and open source headless content management system. Prior to version 3.78.0 in @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, and @payloadcms/storage-s3, the client-upload signed-URL endpoints for S3, GCS, Azure, and R2 did not properly sanitize filenames. An attacker could craft filenames to escape the intended storage location. This issue has been patched in version 3.78.0 for @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, and @payloadcms/storage-s3.

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

Path traversal vulnerability in Payload CMS storage plugins (@payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, @payloadcms/storage-s3) where signed-URL endpoints for client-upload did not sanitize filenames, allowing attackers to craft filenames that escape the intended storage location and write files to arbitrary paths in cloud storage.

MitigationUpgrade to version 3.78.0 or later of the affected @payloadcms/storage-* packages and verify file upload functionality continues to work correctly with various filename patterns.

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
PayloadApplication
Affected:< 3.78.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

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

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 installed Payload CMS storage packages
    Run 'npm list @payloadcms/storage-azure @payloadcms/storage-gcs @payloadcms/storage-r2 @payloadcms/storage-s3' or check package.json dependencies for any @payloadcms/storage-* packages
    Affected if Any of these four storage packages are installed in the project
  2. Check version of storage packages
    Run 'npm list @payloadcms/storage-azure' (and other storage packages) to see installed version numbers
    Affected if Any installed storage package version is below 3.78.0
  3. Verify client-upload endpoint is enabled
    Check payload.config.ts for storage configuration - look for 'clientUpload' property set to true in the storage plugin options
    Affected if The storage plugin has clientUpload enabled, making the signed-URL upload endpoint active
  4. Confirm storage adapter is in use
    Review payload.config.ts to ensure the affected storage plugins are actually assigned to a collection's 'upload' or 'files' configuration
    Affected if Collections are configured to use one of the vulnerable storage adapters for file uploads

You are affected if you have any @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, or @payloadcms/storage-s3 package installed with version below 3.78.0 and have client-upload enabled for that storage configuration.

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 3.78.0 or later
Fixed in 3.78.0
Interim mitigation

Upgrade to version 3.78.0 or later of the affected @payloadcms/storage-* packages and verify file upload functionality continues to work correctly with various filename patterns.

Recommended fix High confidence

@payloadcms/[email protected], @payloadcms/[email protected], @payloadcms/[email protected], @payloadcms/[email protected]

  1. Identify which Payload storage plugin(s) are in use: @payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, or @payloadcms/storage-s3
  2. Run npm update for the specific storage package(s) to version 3.78.0 (e.g., npm install @payloadcms/[email protected])
  3. Alternatively, run npm update @payloadcms/storage-s3 @payloadcms/storage-gcs @payloadcms/storage-azure @payloadcms/storage-r2 to update all at once
  4. Verify the installed version matches 3.78.0 using npm list <package-name>
  5. Test that file uploads via the client-upload signed-URL endpoints work correctly

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

Fix this in Payload Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34750 — 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-34750 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