All vulnerabilities
CVE-2026-105866GHSA-v5gf-vpjc-pc7w

Payload: Unauthenticated account-lockout denial of service

payloadcms payloadnpmLibraries & packages
Open in ThreatlineRecord JSON
CVSS
6.9Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.37%Chance of exploitation activity in the next 30 days, higher than 30% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in3.90.0Also 4.0.0-canary.34GitHub
Published6 Oct 2026Updated 7 Oct 2026CVE List

What fixes it

  • 3.90.0payload, npmGitHubnpm install payload@3.90.0
  • 4.0.0-canary.34payload, npmGitHubnpm install payload@4.0.0-canary.34

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from GitHub Advisory Database

Affected versions 6

  • payload, npm< 3.90.0GitHub
  • payload, npm>= 4.0.0-canary.0, < 4.0.0-canary.34GitHub
  • payloadaffected: < 3.90.0CVE List
  • payloadaffected: >= 4.0.0-canary.0, < 4.0.0-canary.34CVE List
  • payload, npmfrom first release, fixed in 3.90.0OSV
  • payload, npmfrom 4.0.0-canary.0, fixed in 4.0.0-canary.34OSV

References 5