Skip to main content
VulnerabilityPublished

CVE-2026-105860: payloadcms payload · Missing Authorization

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.1% chance of exploitation in 30 days – higher than 9% 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:N/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.90.0
Fixed in
  • 3.90.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • <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 to PayloadCMS plugin-multi-tenant version 3.90.0 or later, or 4.0.0-canary.34 or later, where the issue is fixed. Deployments that have replaced the default tenant array field access with secured arrayFieldAccess.create and update functions are not affected and require no further action.

Description

## Impact When using the default tenant array field access, an authenticated user could assign themselves to other tenants. **You are affected if:** - You are using `@payloadcms/plugin-multi-tenant` If you configure the tenants arrayFieldAccess.create/update functions, a secured replacement membership field, you are not affected by this specific default behavior. ## Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ## Workarounds Configure tenants arrayFieldAccess.create and tenants arrayFieldAccess.update so only trusted users authorized for all tenants can modify memberships.

References

Community reviews

Loading reviews…