CVE-2026-34750: Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints
Impact 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. Consumers are affected if ALL of these are true: - Payload version < v3.78.0 - Using client-upload signed-URL endpoints for any supported storage adapter ## Patches This vulnerability has been patched in v3.78.0.
Published Apr 1, 2026
Affected packages
@payloadcms/storage-azure
- Ecosystem
- npm
- Affected
- < 3.78.0
- Fixed in
- 3.78.0
- Check
npm ls @payloadcms/storage-azure
@payloadcms/storage-gcs
- Ecosystem
- npm
- Affected
- < 3.78.0
- Fixed in
- 3.78.0
- Check
npm ls @payloadcms/storage-gcs
@payloadcms/storage-r2
- Ecosystem
- npm
- Affected
- < 3.78.0
- Fixed in
- 3.78.0
- Check
npm ls @payloadcms/storage-r2
@payloadcms/storage-s3
- Ecosystem
- npm
- Affected
- < 3.78.0
- Fixed in
- 3.78.0
- Check
npm ls @payloadcms/storage-s3
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
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.
Consumers are affected if ALL of these are true:
- Payload version < v3.78.0
- Using client-upload signed-URL endpoints for any supported storage adapter
Patches
This vulnerability has been patched in v3.78.0. Filename validation has been hardened for client uploads.
Consumers should upgrade to v3.78.0 or later.
Workarounds
Consumers can upgrade:
- Limit access to client-upload signed-URL endpoints to trusted users only.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
