CVE-2026-105804: payloadcms payload · Weak Password Hashing
Affects payloadcms payloadSource CVE Database V5
Not known to be exploited · CVSS 5.7 Medium : upgrade to 4.0.0-canary.34 or 3.90.0 when convenient.
Data as of 19 Nov 2026, 20:25 UTC
- EPSS
- 0.08% chance of exploitation in 30 days – higher than 0% 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:L/AC:H/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| payloadcmspayload | Affected
| Fixed in
|
| payloadcmspayload | Affected
| Fixed in
|
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to PayloadCMS version 3.90.0 or later, or 4.0.0-canary.34 or later, where the PBKDF2 work factor has been increased to recommended levels. Applying these updates will mitigate the vulnerability by strengthening password hash computational effort.
Description
### Impact The password-hashing configuration used a lower work factor than what is recommended. ### Patches Payload now uses stronger password-hashing parameters and transparently upgrades older hashes following a successful login. Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Upgrading is recommended. Until you can upgrade, protect database copies and backups from unauthorized access and require strong, unique passwords.