CVE-2026-34750: Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints

Published Apr 1, 2026
·
Updated

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.

Other sources

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.

— MITRE

Affected Software

5 affected componentsFixes available
npm/@payloadcms/storage-s3<3.78.0
3.78.0
npm/@payloadcms/storage-r2<3.78.0
3.78.0
npm/@payloadcms/storage-gcs<3.78.0
3.78.0
npm/@payloadcms/storage-azure<3.78.0
3.78.0
PayloadCMS Payload Node.js<3.78.0

Event History

Apr 1, 2026
CVE Published
via MITRE·07:51 PM
Data Sourced
via MITRE·07:51 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·08:16 PM
Affected Software
Advisory Published
via GitHub·09:44 PM
Data Sourced
via GitHub·09:44 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-34750?

The severity of CVE-2026-34750 is considered high due to its potential to allow attackers to manipulate file paths.

2

How do I fix CVE-2026-34750?

To fix CVE-2026-34750, update to version 3.78.0 or later of the affected packages.

3

Which systems are affected by CVE-2026-34750?

CVE-2026-34750 affects systems using @payloadcms/storage-s3, @payloadcms/storage-r2, @payloadcms/storage-gcs, and @payloadcms/storage-azure versions below 3.78.0.

4

What type of attack does CVE-2026-34750 allow?

CVE-2026-34750 allows attackers to craft filenames that could escape the intended storage location, potentially accessing unauthorized data.

5

What platforms are involved in CVE-2026-34750?

CVE-2026-34750 involves platforms such as S3, GCS, Azure, and R2 through the Vulnerable payload CMS endpoints.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203