CVE-2026-105860: Payload: 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.
Other sources
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 default tenant array field access allows an authenticated user to assign the user's own account to other tenants. Deployments that replace the default behavior with secured tenants arrayFieldAccess.create and tenants arrayFieldAccess.update functions are not affected by this behavior. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/@payloadcms/plugin-multi-tenantto a version that resolves this vulnerability.Fixed in 4.0.0-canary.34 - Upgrade
Upgrade
npm/@payloadcms/plugin-multi-tenantto a version that resolves this vulnerability.Fixed in 3.90.0 - Upgrade
Upgrade
@payloadcms/plugin-multi-tenantto a version that resolves this vulnerability.Fixed in 3.90.0 - Upgrade
Upgrade
@payloadcms/plugin-multi-tenantto a version that resolves this vulnerability.Fixed in 4.0.0-canary.34 - Configuration
Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.
@payloadcms/plugin-multi-tenant tenants arrayFieldAccess.create and tenants arrayFieldAccess.update = secured access functions
Event History
Frequently Asked Questions
Which deployments are affected?
Deployments using @payloadcms/plugin-multi-tenant before version 3.90.0, or canary builds before 4.0.0-canary.34, are affected if they retain the default tenant array field access behavior. Deployments with secured tenants arrayFieldAccess.create and tenants arrayFieldAccess.update functions are not affected.
What access does an attacker need?
An attacker needs an authenticated user account. They can use the default tenant array field access behavior to assign their own account to other tenants.
What should be done to remediate the issue?
Upgrade to @payloadcms/plugin-multi-tenant 3.90.0 or later, or to 4.0.0-canary.34 or later for canary deployments. If upgrading is not immediately possible, replace the default tenant array field access behavior with secured tenants arrayFieldAccess.create and tenants arrayFieldAccess.update functions.