CVE-2026-105863: 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.
Other sources
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 authentication claim name can place unintended values in the authentication token issued at login. This issue is fixed in version 3.90.0.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/payloadto a version that resolves this vulnerability.Fixed in 4.0.0-canary.34 - Upgrade
Upgrade
npm/payloadto a version that resolves this vulnerability.Fixed in 3.90.0 - Upgrade
Upgrade
Payloadto a version that resolves this vulnerability.Fixed in 3.90.0
Event History
Frequently Asked Questions
Which deployments are affected?
Payload versions after 3.0.0 and before 3.90.0 are affected when a custom field option maps a field to a reserved authentication claim name. Version 3.90.0 fixes the issue.
What configuration condition is required for exploitation?
The affected condition is a custom field option mapped to a reserved authentication claim name. That mapping can cause unintended values to be included in authentication tokens issued at login.
How can I determine whether my instance is exposed?
Check whether the deployed Payload version is greater than 3.0.0 and less than 3.90.0, then review custom field options for mappings to reserved authentication claim names. Instances without that configuration condition are not described as affected by the provided information.
What is the recommended remediation?
Upgrade Payload to version 3.90.0. If an immediate upgrade is not possible, review and remove or change custom field mappings that use reserved authentication claim names.