Skip to main content
VulnerabilityPublished

CVE-2026-105846: payloadcms payload · Open Redirect

Affects payloadcms payloadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 4.0.0-canary.27 or 3.88.0 when convenient.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-canary.27, 3.88.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A: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 next and payloadcms/payload to 4.0.0-canary.27 or 3.88.0.

Affected software

ProductAffectedFixed in
payloadcmspayloadAffected
  • >=4.0.0-canary.0 <4.0.0-canary.27
Fixed in
  • 4.0.0-canary.27
payloadcmspayloadAffected
  • >=3.40.0 <3.88.0
Fixed in
  • 3.88.0
@payloadcmsnextAffected
  • >=4.0.0-canary.0 <4.0.0-canary.27
Fixed in
  • 4.0.0-canary.27
@payloadcmsnextAffected
  • >=3.31.0 <3.88.0
Fixed in
  • 3.88.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • >=3.31.0 <3.88.0
  • >=3.40.0 <3.88.0
  • >=4.0.0-canary.0 <4.0.0-canary.27
Fixed in
  • 3.88.0
  • 4.0.0-canary.27

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.88.0 or later, or 4.0.0-canary.27 or later, where this open redirect vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

Description

### Impact Under certain conditions, an attacker can craft a redirect link that sends a guest user to an untrusted destination after authenticating. ### Patches Users should upgrade Payload packages to `>= 3.88.0` or `>= 4.0.0-canary.27`. ### Workarounds Upgrading is recommended. Until then, remove user-controlled redirect values from authentication flows or restrict them to known local paths.

References

Community reviews

Loading reviews…