CVE-2026-105866 payloadcms CVE debrief

Who should care

Defenders responsible for Payload installations, particularly those using local authentication and account lockout, should assess exposure and prioritize upgrading to >= 3.90.0 or >= 4.0.0-canary.34. This includes operators, platform administrators, vulnerability management teams, and security teams who need to verify affected versions and exposure, and plan for upgrades and patches.

Why it matters

CVE-2026-105866 is a denial of service vulnerability in Payload that can be triggered by an unauthenticated attacker, potentially leading to service disruption and increased help desk requests. Defenders should prioritize upgrading to >= 3.90.0 or >= 4.0.0-canary.34 and verify affected versions and exposure.

• Denial of service for legitimate users
• Potential for increased help desk requests
• Need for verification of affected versions and exposure
• Prioritization of upgrades and patches

Technical summary

An unauthenticated attacker who knows an account's email address or username could trigger Payload's account lockout mechanism and prevent that user from signing in. You are affected if using an affected Payload version with an auth-enabled collection that uses local authentication and account lockout. Successful password resets now clear the account's lockout state, and the forgot-password flow enforces a configurable minimum interval between reset emails. Defenders should assess exposure and prioritize upgrading to >= 3.90.0 or >= 4.0.0-canary.34.

Defensive priority

Defenders should prioritize upgrading Payload packages to >= 3.90.0 or >= 4.0.0-canary.34 to prevent unauthenticated account-lockout denial of service.

Recommended defensive actions

• Upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34
• Review and update auth-enabled collections that use local authentication and account lockout
• Monitor for potential denial of service attacks
• Verify affected Payload versions and exposure
• Prioritize upgrades and patches for affected deployments
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability, including the impact, patches, and affected versions. The vulnerability was publicly disclosed on 2026-10-07T20:29:04.000Z. Defenders should verify affected Payload versions and upgrade to >= 3.90.0 or >= 4.0.0-canary.34. The source item and CVE record do not provide additional information on exploitability or affected deployments.

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.