Skip to main content
VulnerabilityPublished

CVE-2026-105867: payloadcms payload · Insecure Direct Object Reference

Affects payloadcms payloadSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% 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:N/VI:H/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 storage-s3 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
@payloadcmsstorage-s3Affected
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 4.0.0-canary.34
@payloadcmsstorage-s3Affected
  • <3.90.0
Fixed in
  • 3.90.0

AI-suggested

A fix is available in PayloadCMS versions 3.90.0 and 4.0.0-canary.34. Users should upgrade to these versions or later to remediate this vulnerability. Since this is a cloud-hosted service, the vendor manages remediation for the cloud service; users should verify with the vendor advisory for confirmation of patch deployment. Until patched, ensure that useCompositePrefixes is enabled or properly configured to prevent this bypass.

Description

### Impact An authenticated user could overwrite an existing S3 object belonging to another upload collection, bypassing that collection’s access controls and prior file validation. You are affected if ALL of these are true: - Client uploads are enabled for multiple collections that share an S3 bucket. - useCompositePrefixes is not configured or is set to `false`. ### Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds Disable client uploads until you can upgrade.

References

Community reviews

Loading reviews…