CVE-2026-105863: Payload authentication token field handling issue

Published Oct 6, 2026
·
Updated

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

38 affected componentsFixes available
Payload Payload>3.0.0<3.90.0
npm/payload>=4.0.0-canary.0<4.0.0-canary.34
4.0.0-canary.34
npm/payload>=3.0.0<3.90.0
3.90.0
PayloadCMS Payload Node.js>=3.0.0<3.90.0
PayloadCMS Payload Node.js=4.0.0-canary0
PayloadCMS Payload Node.js=4.0.0-canary1
PayloadCMS Payload Node.js=4.0.0-canary10
PayloadCMS Payload Node.js=4.0.0-canary11
PayloadCMS Payload Node.js=4.0.0-canary12
PayloadCMS Payload Node.js=4.0.0-canary13
PayloadCMS Payload Node.js=4.0.0-canary14
PayloadCMS Payload Node.js=4.0.0-canary15
PayloadCMS Payload Node.js=4.0.0-canary16
PayloadCMS Payload Node.js=4.0.0-canary17
PayloadCMS Payload Node.js=4.0.0-canary18
PayloadCMS Payload Node.js=4.0.0-canary19
PayloadCMS Payload Node.js=4.0.0-canary2
PayloadCMS Payload Node.js=4.0.0-canary20
PayloadCMS Payload Node.js=4.0.0-canary21
PayloadCMS Payload Node.js=4.0.0-canary22
PayloadCMS Payload Node.js=4.0.0-canary23
PayloadCMS Payload Node.js=4.0.0-canary24
PayloadCMS Payload Node.js=4.0.0-canary25
PayloadCMS Payload Node.js=4.0.0-canary26
PayloadCMS Payload Node.js=4.0.0-canary27
PayloadCMS Payload Node.js=4.0.0-canary28
PayloadCMS Payload Node.js=4.0.0-canary29
PayloadCMS Payload Node.js=4.0.0-canary3
PayloadCMS Payload Node.js=4.0.0-canary30
PayloadCMS Payload Node.js=4.0.0-canary31
PayloadCMS Payload Node.js=4.0.0-canary32
PayloadCMS Payload Node.js=4.0.0-canary33
PayloadCMS Payload Node.js=4.0.0-canary4
PayloadCMS Payload Node.js=4.0.0-canary5
PayloadCMS Payload Node.js=4.0.0-canary6
PayloadCMS Payload Node.js=4.0.0-canary7
PayloadCMS Payload Node.js=4.0.0-canary8
PayloadCMS Payload Node.js=4.0.0-canary9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  2. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 3.90.0
  3. Upgrade

    Upgrade Payload to a version that resolves this vulnerability.

    Fixed in 3.90.0

Event History

Oct 6, 2026
CVE Published
via MITRE·04:39 PM
Data Sourced
via MITRE·04:39 PM
DescriptionWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 7, 2026
Advisory Published
via GitHub·08:28 PM
Data Sourced
via GitHub·08:28 PM
DescriptionWeaknessAffected Software
Nov 2, 2026
Exploit Published
via GitHub·04:40 PM

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203