Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-frq9-7j6g-v74x | Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints |
Mon, 13 Apr 2026 19:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:payloadcms:payload:*:*:*:*:*:node.js:*:* |
Thu, 02 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Payloadcms
Payloadcms payload |
|
| Vendors & Products |
Payloadcms
Payloadcms payload |
|
| Metrics |
ssvc
|
Wed, 01 Apr 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints | |
| Weaknesses | CWE-22 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-02T15:33:58.886Z
Reserved: 2026-03-30T19:17:10.225Z
Link: CVE-2026-34750
Updated: 2026-04-02T15:33:32.561Z
Status : Analyzed
Published: 2026-04-01T20:16:27.337
Modified: 2026-04-13T19:15:38.330
Link: CVE-2026-34750
No data.
OpenCVE Enrichment
Updated: 2026-04-14T16:42:06Z
Github GHSA