CVE-2026-93363: @payloadcms/storage-vercel-blob has access control bypass of uploads in Vercel Storage adapter
`@payloadcms/storage-vercel-blob` can let a signed-in user upload files through the client-upload route even when the collection's access rules would forbid it. Only sites with client uploads enabled are affected. Upgrade Payload packages to 3.90.0 or 4.0.0-canary.34.
Published Nov 4, 2026 · Analysis Nov 4, 2026
What an attacker can do
With client uploads on, the Vercel Blob adapter exposes a route that issues upload permission to the browser. In affected versions, access on that route does not consistently match the associated collection's access configuration. An authenticated user whose role cannot create or update documents in an upload collection may still get the right to upload files to your Vercel Blob store.
The attacker needs a valid account that can reach the client-upload route, with low privileges. They need no user interaction. The impact is limited to integrity (CWE-862, missing authorization): unwanted files in your blob storage, with the storage cost and content risk that brings. Nothing in the sources says data can be read or code run.
The fix adds a check. Client uploads now require authentication and the appropriate collection-level access before the upload is granted. A related commit adds a shared helper assertClientUploadAccess, which requires a signed-in user and then runs the collection's create access check, falling back to update. If neither passes, it throws Forbidden.
Applications that do not enable client uploads are not affected.
Who is affected
@payloadcms/storage-vercel-blob from 3.25.0 up to but not including 3.90.0, and 4.0.0-canary.0 up to but not including 4.0.0-canary.34. You are affected only if you use client uploads with this adapter and authenticated users can reach the client-upload route. Check the installed version:
npm ls @payloadcms/storage-vercel-blobThen look for clientUploads in the adapter options in your Payload config.
@payloadcms/storage-vercel-blob
- Ecosystem
- npm
- Affected
- >= 3.25.0, < 3.90.0
- Fixed in
- 3.90.0
- Check
npm ls @payloadcms/storage-vercel-blob
@payloadcms/storage-vercel-blob
- Ecosystem
- npm
- Affected
- >= 4.0.0-canary.0, < 4.0.0-canary.34
- Fixed in
- 4.0.0-canary.34
- Check
npm ls @payloadcms/storage-vercel-blob
How to fix it
Upgrade Payload packages to 3.90.0 or later, or to 4.0.0-canary.34 or later on the canary line. Keep all @payloadcms/* packages on the same version.
npm install @payloadcms/[email protected]If you cannot upgrade yet, the advisory says to disable client uploads, or to configure the upload route's access control so it enforces the associated collection's permissions.
How to tell if you were hit
Review your Vercel Blob store for files created by users whose role should not upload to the collection. Compare blob creation times with your Payload upload collection records: blobs with no matching document may be uploads that bypassed the check. Check application logs for requests to the client-upload route from low-privilege accounts.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
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 patched version is recommended. Until you can upgrade, disable client uploads or configure the upload route’s access control to enforce the associated collection’s permissions.
Credited to wsparks-vc.
Questions
- Am I affected if I do not use client uploads?
No. The advisory says applications that do not enable client uploads are not affected.
- Does the attacker need an account?
Yes. The user must be authenticated and able to reach the client-upload route. The CVSS vector marks low privileges required.
- Which versions fix CVE-2026-93363?
3.90.0 on the 3.x line and 4.0.0-canary.34 on the 4.x canary line.
- Is there a workaround?
Yes. Disable client uploads, or set the upload route's access control to enforce the collection's permissions. Upgrading is recommended.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
