1vulnerability
- Critical0 (0.0%)
- High0 (0.0%)
- Medium0 (0.0%)
- Moderate1 (100.0%)
- Low0 (0.0%)
payloadcms-storage-vercel-blob
Ecosystem: npm
Downloads:
- 0CriticalAffects 0 versions
- 0HighAffects 0 versions
- 0MediumAffects 0 versions
- 1ModerateAffects 2 versions
- 0LowAffects 0 versions
Monthly breakdown
- 1 vulnerabilities
- Critical: 0
- High: 0
- Medium: 0
- Moderate: 1
- Low: 0
Vulnerabilities (1)
Known vulnerabilities affecting payloadcms-storage-vercel-blob, based on data from OSV.
| ID | Severity | Summary | Affected versions | Published | Source |
|---|---|---|---|---|---|
| GHSA-mc8m-rr6c-r5qr | Moderate | @payloadcms/storage-vercel-blob has access control bypass of uploads in Vercel Storage adapter### Impact In affected configurations, client upload access does not consistently align with the associated collection’s access configuration. You are affected if: - You use client uploads with `@payloadcms/storage-vercel-blob`. - Authenticated users can access the client-upload route. Applications that do not enable client uploads are not affected. ### Patches Client uploads now require authentication and the appropriate collection-level access before upload access is granted. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Upgrading to a pat |
| GitHub (opens in a new tab) |
- GHSA-mc8m-rr6c-r5qrModerate@payloadcms/storage-vercel-blob has access control bypass of uploads in Vercel Storage adapter
>= 3.25.0, < 3.90.0>= 4.0.0-canary.0, < 4.0.0-canary.34
### Impact In affected configurations, client upload access does not consistently align with the associated collection’s access configuration. You are affected if: - You use client uploads with `@payloadcms/storage-vercel-blob`. - Authenticated users can access the client-upload route. Applications that do not enable client uploads are not affected. ### Patches Client uploads now require authentication and the appropriate collection-level access before upload access is granted. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Upgrading to a pat
CVE: CVE-2026-93363