Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints
Exact source revision recorded 24 Oct 2026 13:17:17 UTC. It does not establish the source's current position. Latest evidence.
osv · GHSA-frq9-7j6g-v74x
Published### 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.
- Source published
- 1 Apr 2026 21:44:09 UTC
- Source modified
- 1 Apr 2026 21:56:20 UTC
- Observed here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Publisher rating · MODERATE