CVE-2026-105847: Payload: Polymorphic join queries could disclose hidden fields

Published Oct 6, 2026
·
Updated

Impact

A user with query access could use polymorphic join filters to infer hidden or read-restricted field values, including password-reset tokens.

You are affected if:

- You use an affected Payload version. - Users can query a collection with a polymorphic join to sensitive fields.

Patches

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

Workarounds

There is no complete workaround. Restricting read access to sensitive collections reduces exposure but does not replace upgrading.

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, a user who can query a collection with a polymorphic join to sensitive fields can infer hidden or read-restricted values, including password-reset tokens, through polymorphic join filters. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

— MITRE

Affected Software

38 affected componentsFixes available
Payload Payload CMS>=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

    Restrict read access to sensitive collections to reduce exposure.

Event History

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

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Payload versions from 3.0.0 before 3.90.0 and 4.0.0 canary versions before 4.0.0-canary.34 are affected. Exposure requires users who can query a collection that has a polymorphic join to sensitive fields.

2

What level of access does an attacker need?

An attacker needs query access to a relevant collection. They can use polymorphic join filters to infer values from fields that are hidden or otherwise read-restricted, including password-reset tokens.

3

What should be done if an immediate upgrade is not possible?

There is no complete workaround. Restrict read access to sensitive collections to reduce exposure, but upgrade Payload packages to 3.90.0 or later, or 4.0.0-canary.34 or later, as soon as possible.

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