CVE-2026-105860: Payload: Tenant authorization bypass in Multi-Tenant Plugin

Published Oct 6, 2026
·
Updated

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

38 affected componentsFixes available
npm/@payloadcms/plugin-multi-tenant<3.90.0, <4.0.0-canary.34
npm/@payloadcms/plugin-multi-tenant>=4.0.0-canary.0<4.0.0-canary.34
4.0.0-canary.34
npm/@payloadcms/plugin-multi-tenant<3.90.0
3.90.0
PayloadCMS Payload Node.js<3.90.0
PayloadCMS Payload Node.js=4.0.0-canary0
PayloadCMS Payload Node.js=4.0.0-canary1
PayloadCMS Payload Node.js=4.0.0-canary10
PayloadCMS Payload Node.js=4.0.0-canary11
PayloadCMS Payload Node.js=4.0.0-canary12
PayloadCMS Payload Node.js=4.0.0-canary13
PayloadCMS Payload Node.js=4.0.0-canary14
PayloadCMS Payload Node.js=4.0.0-canary15
PayloadCMS Payload Node.js=4.0.0-canary16
PayloadCMS Payload Node.js=4.0.0-canary17
PayloadCMS Payload Node.js=4.0.0-canary18
PayloadCMS Payload Node.js=4.0.0-canary19
PayloadCMS Payload Node.js=4.0.0-canary2
PayloadCMS Payload Node.js=4.0.0-canary20
PayloadCMS Payload Node.js=4.0.0-canary21
PayloadCMS Payload Node.js=4.0.0-canary22
PayloadCMS Payload Node.js=4.0.0-canary23
PayloadCMS Payload Node.js=4.0.0-canary24
PayloadCMS Payload Node.js=4.0.0-canary25
PayloadCMS Payload Node.js=4.0.0-canary26
PayloadCMS Payload Node.js=4.0.0-canary27
PayloadCMS Payload Node.js=4.0.0-canary28
PayloadCMS Payload Node.js=4.0.0-canary29
PayloadCMS Payload Node.js=4.0.0-canary3
PayloadCMS Payload Node.js=4.0.0-canary30
PayloadCMS Payload Node.js=4.0.0-canary31
PayloadCMS Payload Node.js=4.0.0-canary32
PayloadCMS Payload Node.js=4.0.0-canary33
PayloadCMS Payload Node.js=4.0.0-canary4
PayloadCMS Payload Node.js=4.0.0-canary5
PayloadCMS Payload Node.js=4.0.0-canary6
PayloadCMS Payload Node.js=4.0.0-canary7
PayloadCMS Payload Node.js=4.0.0-canary8
PayloadCMS Payload Node.js=4.0.0-canary9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/@payloadcms/plugin-multi-tenant to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  2. Upgrade

    Upgrade npm/@payloadcms/plugin-multi-tenant to a version that resolves this vulnerability.

    Fixed in 3.90.0
  3. Upgrade

    Upgrade @payloadcms/plugin-multi-tenant to a version that resolves this vulnerability.

    Fixed in 3.90.0
  4. Upgrade

    Upgrade @payloadcms/plugin-multi-tenant to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  5. 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

Oct 6, 2026
CVE Published
via MITRE·04:33 PM
Data Sourced
via MITRE·04:33 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 7, 2026
Advisory Published
via GitHub·08:29 PM
Data Sourced
via GitHub·08:29 PM
DescriptionWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203