Skip to content
Fencer Intel
medium 6.5

CVE-2026-34750 json

Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints

published 7mo ago modified 15d ago also EUVD-2026-18019 , GHSA-frq9-7j6g-v74x

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 29%
public exploits
0
none known

Summary

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.

Patch / fix

  • npm @payloadcms/storage-azure 3.78.0
  • npm @payloadcms/storage-gcs 3.78.0
  • npm @payloadcms/storage-r2 3.78.0
  • npm @payloadcms/storage-s3 3.78.0
  • payloadcms payload 3.78.0

Is CVE-2026-34750 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7mo ago

Exploit prediction

0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

Affected packages

ecosystem package affected fixed in
npm @payloadcms/storage-azure
<3.78.0
3.78.0
npm @payloadcms/storage-gcs
<3.78.0
3.78.0
npm @payloadcms/storage-r2
<3.78.0
3.78.0
npm @payloadcms/storage-s3
<3.78.0
3.78.0

Affected products

  • payloadcms payload

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.