CVE-2026-106100: Payload: Field-level write access bypass in Payload on MongoDB

Published Oct 6, 2026
·
Updated

Impact A vulnerability in field-level access control could allow an authenticated user to modify fields they are not permitted to change on documents they can otherwise update.

You are affected if: Payload version < 3.87.0 (or a 4.0.0-canary release before 4.0.0-canary.20) using the MongoDB adapter (@payloadcms/db-mongodb) with any collection that relies on field-level access control to restrict writes under certain conditions.

Relational adapters (Postgres, SQLite) are not affected.

Patches Handling of incoming field data has been hardened so field-level access control is enforced consistently.

Users should upgrade to 3.87.0 (or 4.0.0-canary.20 on the 4.x line) or later.

Workarounds There is no complete workaround. Upgrading to 3.87.0 (or 4.0.0-canary.20 on the 4.x line) is recommended.

Other sources

Payload is a free and open source headless content management system. In @payloadcms/db-mongodb versions before 3.87.0 and canary versions before 4.0.0-canary.20, an authenticated user who can update a document can modify fields that field-level write access control does not permit that user to change. The Postgres and SQLite adapters are not affected. This issue is fixed in versions 3.87.0 and 4.0.0-canary.20.

— MITRE

Affected Software

24 affected componentsFixes available
npm/@payloadcms/db-mongodb<3.87.0, <4.0.0-canary.20
npm/@payloadcms/db-mongodb>=4.0.0-canary.0<4.0.0-canary.20
4.0.0-canary.20
npm/@payloadcms/db-mongodb<3.87.0
3.87.0
PayloadCMS Payload Node.js<3.87.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-canary3
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/@payloadcms/db-mongodb to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.20
  2. Upgrade

    Upgrade npm/@payloadcms/db-mongodb to a version that resolves this vulnerability.

    Fixed in 3.87.0
  3. Upgrade

    Upgrade @payloadcms/db-mongodb to a version that resolves this vulnerability.

    Fixed in 3.87.0

Event History

Oct 6, 2026
CVE Published
via MITRE·04:56 PM
Data Sourced
via MITRE·04:56 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
DescriptionSeverityWeakness
Oct 7, 2026
Advisory Published
via GitHub·04:19 PM
Data Sourced
via GitHub·04:19 PM
DescriptionSeverityWeaknessAffected Software
Oct 15, 2026
Data Sourced
via NVD·12:07 AM
RemedyAffected Software

Frequently Asked Questions

1

Which deployments are affected?

Only Payload deployments using the @payloadcms/db-mongodb adapter are affected. The Postgres and SQLite adapters are not affected.

2

What level of access does an attacker need?

An attacker must be authenticated and already have permission to update a document. They can then modify fields for which field-level write access control should deny them write permission.

3

What versions contain the fix?

Upgrade the MongoDB adapter to version 3.87.0 or later, or to 4.0.0-canary.20 or later for canary releases.

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