Payload authentication token field handling issue
### 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`.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-105863US | critical9.4 | — | ||
Payload is a free and open source headless content management system. In versions after 3.0.0 and before 3.90.0, a custom field option that maps a field to a reserved authenticatio… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/payloadcms/payloadPACKAGE
- https://github.com/payloadcms/payload/commit/56cd5cd050a57daebf33159e41e5ff9d4a45239cWEB
- https://github.com/payloadcms/payload/releases/tag/v3.90.0WEB
- https://github.com/payloadcms/payload/security/advisories/GHSA-66wr-7vmr-p5jqWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-105863ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan