CVE-2026-105864 payloadcms CVE debrief

Who should care

Defenders using @payloadcms/plugin-multi-tenant should assess exposure and prioritize upgrades. This includes reviewing current configurations, verifying tenant access controls, and implementing compensating controls if necessary. Security teams should track exceptions, retest remediated assets, and ensure evidence is documented before closing the issue.

Why it matters

CVE-2026-105864 allows authenticated users to create records in another tenant, requiring defenders to assess exposure and prioritize upgrades.

• Verify tenant access controls to prevent unauthorized record creation
• Upgrade @payloadcms/plugin-multi-tenant to prevent cross-tenant record creation
• Implement access control with accessResultOverride on multi-tenant collection config

Technical summary

Authenticated users limited to one tenant can create records in another tenant using @payloadcms/plugin-multi-tenant with at least one tenant-enabled collection. This requires specific configurations and allows bypassing normal access controls. Users should upgrade to Payload packages >= 3.90.0 or >= 4.0.0-canary.34 to mitigate the issue. The vulnerability does not allow unauthorized reads or direct edits to existing documents in the target tenant. Affected users should assess their exposure and prioritize upgrades.

Defensive priority

Defenders should prioritize upgrading @payloadcms/plugin-multi-tenant to prevent cross-tenant record creation.

Recommended defensive actions

• Upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34
• Implement access control with accessResultOverride on multi-tenant collection config
• Verify tenant access controls to prevent unauthorized record creation
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability and mitigation steps. The issue is specific to @payloadcms/plugin-multi-tenant and requires at least one tenant-enabled collection. Users should verify their deployment and assess exposure. The vulnerability does not allow reads or direct edits to existing target-tenant documents.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.