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**. 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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-34750US | — | — | ||
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 @pa… | ||||
references
External citations — patches, advisories, analysis.
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan