Vulnerability in @payloadcms/plugin-multi-tenant (CVE-2026-105860)
Summary
Vulnerability in @payloadcms/plugin-multi-tenant (CVE-2026-105860). Data can be tampered with by attackers. Mitigation: upgrade to 4.0.0-canary.34 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-105860 has been found in @payloadcms/plugin-multi-tenant.
Data can be tampered with by attackers. CVSS score: 7.1/10.
What to do: upgrade @payloadcms/plugin-multi-tenant to 4.0.0-canary.34 or later.
If unsure, ask your IT team or search "@payloadcms/plugin-multi-tenant CVE-2026-105860" on the vendor's site.
CVE-2026-105860 (@payloadcms/plugin-multi-tenant) — CWE-862 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.0.0-canary.34 — apply immediately
Workaround: Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in @payloadcms/plugin-multi-tenant.
Check the vendor advisory for the affected versions of @payloadcms/plugin-multi-tenant.
Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.
Update to 4.0.0-canary.34.
Workaround: Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@payloadcms/plugin-multi-tenant' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@payloadcms/plugin-multi-tenant' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@payloadcms/plugin-multi-tenantを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.パッチが適用されるまでの応急処置として、Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade @payloadcms/plugin-multi-tenant to 4.0.0-canary.34ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- patch security-advisories@github.com
- patch security-advisories@github.com
- patch security-advisories@github.com
- web nvd.nist.gov
- web github.com