Skip to main content
VulnerabilityPublished

CVE-2026-105849: payloadcms payload · Insertion of Sensitive Information Into Sent Data

Affects payloadcms payloadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 4.0.0-canary.34 or 3.90.0 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% 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:P/PR:L/UI:N/VC:H/VI:H/VA:H/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.0.0 <3.90.0
Fixed in
  • 3.90.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • >=3.0.0 <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, where this vulnerability is fixed. Until then, rotate or disable API keys regularly to limit the window of exposure. No other specific mitigations are indicated.

Description

### Impact Users with read access to other user documents could access their active API keys. An exposed key grants the target account’s permissions until rotated or disabled. You are affected if: - An authentication collection enables `useAPIKey`. - Users have read access to other user documents containing active API keys. ### Patches Users should upgrade payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Disable `useAPIKey` or restrict users to reading only their own authentication document. Rotate any API key that may have been exposed.

References

Community reviews

Loading reviews…