CVE-2026-105853: payloadcms payload · Information Exposure
Affects payloadcms payloadSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 4.0.0-canary.34 or 3.90.0 soon.
Data as of 20 Nov 2026, 17:34 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 17% 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:L/UI:N/VC:H/VI:N/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 PayloadCMS 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 additional mitigation is required once upgraded.
Description
PayloadCMS versions from 3.0.0 up to but not including 3.90.0, and canary versions from 4.0.0-canary.0 up to but not including 4.0.0-canary.34, contain a vulnerability where token refresh and password reset responses may expose hidden or read-restricted fields to unauthorized users. This exposure allows sensitive information leakage. The issue is resolved in versions 3.90.0 and 4.0.0-canary.34.