GitHub Advisoryadvisory · npm

GHSA-frq9-7j6g-v74x Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints

MEDIUM Published 2026-04-01 Modified 2026-04-01 Official page ↗
Aliases
CVE-2026-34750
Ecosystem
npm
Packages
@payloadcms/storage-azure, @payloadcms/storage-gcs, @payloadcms/storage-r2, @payloadcms/storage-s3
Severity
Moderate
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Weaknesses
CWE-22
Reviewed
2026-04-01

Affected packages

• npm @payloadcms/storage-azure: < 3.78.0 → fixed in 3.78.0 • npm @payloadcms/storage-gcs: < 3.78.0 → fixed in 3.78.0 • npm @payloadcms/storage-r2: < 3.78.0 → fixed in 3.78.0 • npm @payloadcms/storage-s3: < 3.78.0 → fixed in 3.78.0

Description

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.

Related

Alias · CVE (1)

  • CVE-2026-34750 Payload is a free and open source headless content management system. vulnerability

Weakness · CWE (1)

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

References