Skip to content
Fencer Intel
medium 6.1

CVE-2026-105846 json

Payload: Untrusted redirect URL parameter exploit

published last mo. modified 26d ago also GHSA-w84c-53h3-mc2g , EUVD-2026-93488

cvss
6.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 13%
public exploits
0
none known

Summary

Payload is a free and open source headless content management system. In versions from 3.40.0 before 3.88.0 and canary versions before 4.0.0-canary.27, an attacker can craft a redirect URL parameter that sends a guest user to an untrusted destination after the authentication flow completes. This issue is fixed in versions 3.88.0 and 4.0.0-canary.27.

Patch / fix

  • npm payload 3.88.0, 4.0.0-canary.27
  • npm @payloadcms/next 3.88.0, 4.0.0-canary.27
  • payloadcms payload 3.88.0

Is CVE-2026-105846 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last mo.

Exploit prediction

0.23% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
GitHub 3.1 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
npm payload
>=3.40.0, <3.88.0
>=4.0.0-canary.0, <4.0.0-canary.27
3.88.0
4.0.0-canary.27
npm @payloadcms/next
>=3.31.0, <3.88.0
>=4.0.0-canary.0, <4.0.0-canary.27
3.88.0
4.0.0-canary.27

Affected products

  • payloadcms payload
  • @payloadcms next

Classification

Weakness
  • CWE-601 URL Redirection to Untrusted Site

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.