GHSA-frq9-7j6g-v74x
MEDIUMGHSA-frq9-7j6g-v74x is a medium-severity (CVSS 6.5) Path Traversal vulnerability in @payloadcms/storage-azure. O3 Security confirms whether GHSA-frq9-7j6g-v74x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Payload has Insufficient Filename Validation in Client-Upload Signed-URL Endpoints
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@payloadcms/storage-azurenpm@payloadcms/storage-gcsnpm@payloadcms/storage-r2npmDescription
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @payloadcms/storage-azure | all versions | 3.78.0 |
| 📦npm | @payloadcms/storage-gcs | all versions | 3.78.0 |
| 📦npm | @payloadcms/storage-r2 | all versions | 3.78.0 |
| 📦npm | @payloadcms/storage-s3 | all versions | 3.78.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @payloadcms/storage-azure. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @payloadcms/storage-azure to 3.78.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-frq9-7j6g-v74x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-frq9-7j6g-v74x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-frq9-7j6g-v74x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-frq9-7j6g-v74x in your dependencies?
O3 detects GHSA-frq9-7j6g-v74x across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.