CVE-2026-105855: Payload: Field-level password update restrictions were not enforced
Impact
When an auth collection defined a field-level access.update restriction on the password field, the restriction was not enforced on the server correctly.
Patches
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 before 3.90.0 and canary versions before 4.0.0-canary.34, the server fails to enforce a field-level access.update restriction on the password field of an authentication collection. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
— 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 to a fixed release to a version that resolves this vulnerability.
Fixed in 3.90.0 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 4.0.0-canary.34
Event History
Frequently Asked Questions
Which deployments are affected?
Affected deployments use Payload authentication collections that define a field-level access.update restriction on the password field. Payload versions before 3.90.0, and canary versions before 4.0.0-canary.34, are affected.
What level of access does an attacker need?
The CVSS vector indicates that an attacker needs low privileges and can exploit the issue over the network without user interaction. Exploitation also depends on the target having a password-field access.update restriction that the server fails to enforce.
What is the recommended remediation?
Upgrade Payload packages to version 3.90.0 or later, or to 4.0.0-canary.34 or later for the canary release line. These versions enforce the password field's field-level access.update restriction correctly.