CVE-2026-34750
MEDIUMCVE-2026-34750 is a medium-severity (CVSS 6.5) Path Traversal vulnerability in @payloadcms/storage-azure. O3 Security confirms whether CVE-2026-34750 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
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.
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 CVE-2026-34750 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 CVE-2026-34750 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 CVE-2026-34750. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-34750 in your dependencies?
O3 detects CVE-2026-34750 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.