Skip to main content
VulnerabilityPublished

CVE-2026-105866: payloadcms payload · Improper Restriction of Excessive Authentication Attempts

Affects payloadcms payloadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 4.0.0-canary.34 or 3.90.0 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-canary.34, 3.90.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade payload and payloadcms/payload to 4.0.0-canary.34 or 3.90.0.

Affected software

ProductAffectedFixed in
payloadcmspayloadAffected
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 4.0.0-canary.34
payloadcmspayloadAffected
  • <3.90.0
Fixed in
  • 3.90.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • <3.90.0
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 3.90.0
  • 4.0.0-canary.34

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Payload CMS to version 3.90.0 or later, or to 4.0.0-canary.34 or later. These versions contain the official fix for this vulnerability. No other mitigation is indicated by the vendor advisory.

Description

### **Impact** 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. Applications that do not use Payload local authentication are not affected. ### **Patches** Successful password resets now clear the account’s lockout state. The forgot-password flow also enforces a configurable minimum interval between reset emails, which defaults to 15 seconds. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.

References

Community reviews

Loading reviews…