CVE-2026-105853: Payload: Token refresh and password reset responses may expose restricted user fields

Published Oct 6, 2026
·
Updated

Impact

Token refresh and password reset responses could return fields that the requesting user did not have access to.

You are affected if:

- An authentication collection contains hidden or read-restricted fields.

Patches

Authentication responses now apply field access and hidden-field filtering before returning user documents. Full user documents remain available server-side for access control.

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

Custom authentication strategies remain responsible for filtering user documents returned through custom responses.

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 from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34, token refresh responses and password reset responses can independently return hidden or read-restricted fields that the requesting user cannot access. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

— MITRE

Affected Software

38 affected componentsFixes available
Payload Payload>=3.0.0<3.90.0, <4.0.0-canary.34
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 packages to a version that resolves this vulnerability.

    Fixed in 3.90.0
  4. Upgrade

    Upgrade Payload packages to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  5. Compensating control

    Ensure custom authentication strategies filter user documents returned through custom responses, including hidden or read-restricted fields.

Event History

Oct 6, 2026
CVE Published
via MITRE·04:16 PM
Data Sourced
via MITRE·04:16 PM
DescriptionWeakness
Advisory Published
via GitHub·04:17 PM
Data Sourced
via GitHub·04:17 PM
DescriptionWeaknessAffected Software
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployments are affected?

Affected deployments have an authentication collection with fields that are hidden or restricted by read access. The issue applies to Payload versions from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34.

2

What does an attacker need to do to obtain restricted fields?

The exposure occurs through token refresh and password reset responses. A requesting user can receive hidden or read-restricted fields that they would not otherwise be permitted to access.

3

Are custom authentication strategies covered by the fix?

No. Custom authentication strategies remain responsible for filtering user documents returned in their custom responses.

4

What should be done if patching cannot happen immediately?

There is no complete workaround. Upgrade Payload to version 3.90.0 or later, or to 4.0.0-canary.34 or later.

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