NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

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

highCVSS 4.0 7.1GHSA-p96c-xwx8-3cqj

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.

Published Oct 7, 2026

Affected packages

@payloadcms/plugin-multi-tenant

Ecosystem
npm
Affected
< 3.90.0
Fixed in
3.90.0
Check
npm ls @payloadcms/plugin-multi-tenant

@payloadcms/plugin-multi-tenant

Ecosystem
npm
Affected
>= 4.0.0-canary.0, < 4.0.0-canary.34
Fixed in
4.0.0-canary.34
Check
npm ls @payloadcms/plugin-multi-tenant

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

Credited to meifukun.

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. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries