Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-105864 medium CVSS 4.3

Authorization Flaw in @payloadcms/plugin-multi-tenant (CVE-2026-105864)

Summary

Vulnerability in @payloadcms/plugin-multi-tenant (CVE-2026-105864). Risk of unauthorized operations or information disclosure. Exploitable via accessResultOverride. Mitigation: upgrade to 4.0.0-canary.34 or later.

Original description

The description as published by the source.

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.

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-105864 has been found in @payloadcms/plugin-multi-tenant.
Attackers can target a specific entry point like accessResultOverride over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/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-105864" on the vendor's site.

CVE-2026-105864 (@payloadcms/plugin-multi-tenant) — CWE-863 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: accessResultOverride
Patched: 4.0.0-canary.34 — apply immediately
Workaround: You can add access control with accessResultOverride on the multi-tenant collection config to ensure a user has access to the tenant before creating.
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.

❓ What is the problem

Incorrect authorization (CWE-863) exists in @payloadcms/plugin-multi-tenant. Attackers reach the vulnerable code path via accessResultOverride.

📍 Affected scope

Check the vendor advisory for the affected versions of @payloadcms/plugin-multi-tenant. Attack surface: accessResultOverride.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 4.0.0-canary.34.

🛡️ Workaround

Workaround: You can add access control with accessResultOverride on the multi-tenant collection config to ensure a user has access to the tenant before creating.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    You can add access control with `accessResultOverride` on the multi-tenant collection config to ensure a user has access to the tenant before creating.

    パッチが適用されるまでの応急処置として、You can add access control with accessResultOverride on the multi-tenant collection config to ensure a user has access to the tenant before creating. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade @payloadcms/plugin-multi-tenant to 4.0.0-canary.34

    ステージング環境で 4.0.0-canary.34 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @payloadcms/plugin-multi-tenant
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.0-canary.34"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details