CVE-2026-105864: Payload: Cross-tenant create in @payloadcms/plugin-multi-tenant
Impact An authenticated user limited to one tenant could create a record in another tenant. This requires the multi-tenant plugin with at least one tenant-enabled collection.
Reads and direct edits to an existing target-tenant document were not bypassed.
You are affected if: - You are using @payloadcms/plugin-multi-tenant
Patches Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds You can add access control with accessResultOverride on the multi-tenant collection config to ensure a user has access to the tenant before creating.
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, an authenticated user limited to one tenant can create a record in another tenant when at least one tenant-enabled collection exists. Reads and direct edits of existing documents in the target tenant are not bypassed. 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
Add access control with accessResultOverride on the multi-tenant collection configuration to ensure a user has access to the tenant before creating a record.
@payloadcms/plugin-multi-tenant accessResultOverride = Ensure the user has access to the tenant before creating
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user whose access is limited to one tenant can exploit it. Exploitation also requires that the deployment has at least one tenant-enabled collection.
What can an attacker do, and what remains protected?
The attacker can create a record in a different tenant. The issue does not bypass controls for reading or directly editing existing documents in the target tenant.
Which versions contain the fix?
The issue is fixed in @payloadcms/plugin-multi-tenant version 3.90.0 and 4.0.0-canary.34. Versions before those releases are affected.