CVE-2026-105855: Payload didn't enforce field-level password update restrictions
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.
Published Oct 6, 2026
Affected packages
payload
- Ecosystem
- npm
- Affected
- < 3.90.0
- Fixed in
- 3.90.0
- Check
npm ls payload
payload
- Ecosystem
- npm
- Affected
- >= 4.0.0-canary.0, < 4.0.0-canary.34
- Fixed in
- 4.0.0-canary.34
- Check
npm ls payload
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
Credited to pavelkohout396.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-105858
Payload: Remote Code Execution through first-register
high8.1Oct 7, 2026CVE-2026-105859
Payload: Unauthorized update to collection documents
critical9.8Oct 7, 2026CVE-2026-105861
Payload external upload trust validation issue
high7.2Oct 7, 2026CVE-2026-105862
Payload: Bypassed sanitization of user uploaded SVGs
high8.7Oct 7, 2026CVE-2026-105863
Payload authentication token field handling issue
critical9.2Oct 7, 2026CVE-2026-105865
Payload: Incomplete validation during the upload file lifecycle
high8.1Oct 7, 2026
