Payload has a tenant authorization bypass in Multi-Tenant Plugin
## Impact When using the default tenant array field access, an authenticated user could assign themselves to other tenants. **You are affected if:** - You are using `@payloadcms/plugin-multi-tenant` If you configure the tenants arrayFieldAccess.create/update functions, a secured replacement membership field, you are not affected by this specific default behavior. ## Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ## Workarounds Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-105860US | high7.1OT elevated | — | ||
Payload is a free and open source headless content management system. In @payloadcms/plugin-multi-tenant versions before 3.90.0 and canary versions before 4.0.0-canary.34, the defa… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/payloadcms/payloadPACKAGE
- https://github.com/payloadcms/payload/commit/19b58692d20d3947f31124bf7a88ac14a5ebf02eWEB
- https://github.com/payloadcms/payload/releases/tag/v3.90.0WEB
- https://github.com/payloadcms/payload/security/advisories/GHSA-p96c-xwx8-3cqjWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-105860ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan