Vulnerabilities in pkg:npm/@payloadcms/storage-gcs
PACKAGECVE-2026-34750 is a MODERATE (CVSS 6.5) payload has insufficient filename validation vulnerability (CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) affecting @payloadcms/storage azure libraries in the npm ecosystem. The issue involves payload has insufficient filename validation in client-upload signed-url endpoints. Remediation is available by upgrading affected packages to version 3.78.0.
pkg:npm/@payloadcms/storage-gcs
Vulnerability advisories affecting package pkg:npm/@payloadcms/storage-gcs. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-frq9-7j6g-v74x | CVE-2026-34750 | MODERATE | Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints |
CVE-2026-34750 at a Glance
Security Impact
CVSS: 6.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N).
How to Fix CVE-2026-34750
To remediate this vulnerability, upgrade all affected @payloadcms/storage azure dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install @payloadcms/storage-azure@3.78.0
npm install @payloadcms/storage-gcs@3.78.0
npm install @payloadcms/storage-r2@3.78.0
npm install @payloadcms/storage-s3@3.78.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls @payloadcms/storage-azure
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-34750, inspect your project dependencies using npm:
npm ls @payloadcms/storage-azure
Analyze the terminal output to locate any version of @payloadcms/storage azure in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.78.0), your application is affected.
Note: The npm ls @payloadcms/storage-azure command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), where the product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. In @payloadcms/storage azure, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-34750 Affected @payloadcms/storage azure Versions
4 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
@payloadcms/storage-azure
|
npm |
< 3.78.0
|
3.78.0
|
|
@payloadcms/storage-gcs
|
npm |
< 3.78.0
|
3.78.0
|
|
@payloadcms/storage-r2
|
npm |
< 3.78.0
|
3.78.0
|
|
@payloadcms/storage-s3
|
npm |
< 3.78.0
|
3.78.0
|
References
Frequently Asked Questions
What is CVE-2026-34750?
Which @payloadcms/storage azure versions are affected?
What version fixes CVE-2026-34750?
Is @payloadcms/storage-azure affected?
Is @payloadcms/storage-gcs affected?
What is the CVSS score of CVE-2026-34750?
What CWE is associated with CVE-2026-34750?
How can I check npm dependencies for CVE-2026-34750?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-frq9-7j6g-v74x",
"modified" : "2026-04-01T21:44:09Z",
"published" : "2026-04-01T21:44:09Z",
"aliases" : [ "CVE-2026-34750" ],
"summary" : "Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints",
"details" : "### Impact\n\nThe 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.\n\nConsumers are affected if ALL of these are true:\n\n- Payload version **< v3.78.0**\n- Using client-upload signed-URL endpoints for any supported storage adapter\n\n ## Patches\n\nThis vulnerability has been patched in **v3.78.0**. Filename validation has been hardened for client uploads.\n\nConsumers should upgrade to **v3.78.0** or later.\n\n## Workarounds\n\nConsumers can upgrade:\n\n- Limit access to client-upload signed-URL endpoints to trusted users only.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "@payloadcms/storage-azure"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.78.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@payloadcms/storage-gcs"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.78.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@payloadcms/storage-r2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.78.0"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "@payloadcms/storage-s3"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.78.0"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/payloadcms/payload/security/advisories/GHSA-frq9-7j6g-v74x"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34750"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/payloadcms/payload"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-22" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-04-01T21:44:09Z",
"nvd_published_at" : "2026-04-01T20:16:27Z"
}
}