CVE-2026-105860 · GHSA-p96c-xwx8-3cqj
Payload has a tenant authorization bypass in Multi-Tenant Plugin
- Risk score
- 49/100
- CVSS
- 7.1 v3.1
- Exploit chance (30 days)
- 0.2%
- Published
- 6 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 …
- Affected
- @payloadcms/plugin-multi-tenant (npm) < 3.90.0; @payloadcms/plugin-multi-tenant (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34
- Fix
- Upgrade @payloadcms/plugin-multi-tenant to 3.90.0 or 4.0.0-canary.34 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Story map
At a glance
@payloadcms/plugin-form-builder: Amber, patch this week. Payload is a free and open source headless content management system. In @payloadcms/plugin-form-builder versions before 3.90.0 and canary versions before 4.0.0-canary.34, an attacker can craft a form submission that executes code remotely on the server. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
The flaws
- CVE-2026-105860: Payload has a tenant authorization bypass in Multi-Tenant Plugin (CVSS 7.1 · EPSS 0%)
- CVE-2026-105857: Payload Form Builder has an RCE issue (CVSS 10.0 · EPSS 0%)
- CVE-2026-105859: Payload: Unauthorized update to collection documents (CVSS 9.8 · EPSS 0%)
- CVE-2026-105863: Payload authentication token field handling issue (CVSS 9.4 · EPSS 0%)
The fix
Upgrade @payloadcms/plugin-form-builder: 3.90.0 · 4.0.0 or later on your release line
Who is exposed: @payloadcms/plugin-form-builder (npm) < 3.90.0; @payloadcms/plugin-form-builder (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34
Where it stands
- No known exploitation
Connects to
- Same weakness: Missing authorisation (CWE-862). 398 other warnings in 30 days
- Same product: Earlier @payloadcms/plugin-multi-tenant warnings. 20 in the last 90 days
Why it is Yellow
- CVSS 7.1 high
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| @payloadcms/plugin-multi-tenant | npm | < 3.90.0 | 3.90.0 |
| @payloadcms/plugin-multi-tenant | npm | >= 4.0.0-canary.0, < 4.0.0-canary.34 | 4.0.0-canary.34 |
References
- https://github.com/advisories/GHSA-p96c-xwx8-3cqj
- https://github.com/payloadcms/payload/security/advisories/GHSA-p96c-xwx8-3cqj
- https://nvd.nist.gov/vuln/detail/CVE-2026-105860
- https://github.com/payloadcms/payload/commit/19b58692d20d3947f31124bf7a88ac14a5ebf02e
- https://github.com/payloadcms/payload/releases/tag/v3.90.0
- https://github.com/advisories/GHSA-p96c-xwx8-3cqj
Original description
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.
Last activity 6 Oct 2026. Patch Forecast updates every hour.