All vulnerabilities
CVE-2026-105863GHSA-66wr-7vmr-p5jq

Payload authentication token field handling issue

payloadcms payloadnpmLibraries & packages
Open in ThreatlineRecord JSON
CVSS
9.2Critical
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.38%Chance of exploitation activity in the next 30 days, higher than 30% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in3.90.0Also 4.0.0-canary.34GitHub
Published6 Oct 2026Updated 9 Oct 2026CVE List

What fixes it

  • 3.90.0payload, npmGitHubnpm install payload@3.90.0
  • 4.0.0-canary.34payload, npmGitHubnpm install payload@4.0.0-canary.34

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

Impact

Under certain field configurations, Payload could include unintended values in the authentication token issued at login.

You are affected if:

  • You use an affected Payload version and have configured a custom field option that maps a field to a reserved authentication claim name.

Patches

Payload now restricts which field configuration options can influence the contents of the authentication token.

Users should upgrade payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

Workarounds

There is no complete workaround. Users should upgrade payload packages to >= 3.90.0 or >= 4.0.0-canary.34.

Text from GitHub Advisory Database

Affected versions 6

  • payload, npm>= 3.0.0, < 3.90.0GitHub
  • payload, npm>= 4.0.0-canary.0, < 4.0.0-canary.34GitHub
  • payloadaffected: >= 3.0.0, < 3.90.0CVE List
  • payloadaffected: >= 4.0.0-canary.0, < 4.0.0-canary.34CVE List
  • payload, npmfrom 3.0.0, fixed in 3.90.0OSV
  • payload, npmfrom 4.0.0-canary.0, fixed in 4.0.0-canary.34OSV

References 5