Summary
Payload: Field access control bypass on auth collections
Workarounds
Add a beforeDuplicate field hook to fields and set the value to empty or your default value.
Impact
Payload's duplicate operation copies field values from the source document even when a field is hidden, or its access.read or access.create rule would reject the value for that caller.
The disableDuplicate collection setting, enabled by default on auth collections, did not stop this.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Frequently Asked Questions
- What is CVE-2026-105851? CVE-2026-105851 is a critical-severity incorrect authorization vulnerability in payload (npm), affecting versions > 3.0.0, < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- Which versions of payload are affected by CVE-2026-105851? payload (npm) versions > 3.0.0, < 3.90.0 is affected.
- Is there a fix for CVE-2026-105851? Yes. CVE-2026-105851 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
- Is CVE-2026-105851 exploitable, and should I be worried? Whether CVE-2026-105851 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-105851 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-105851?
- Upgrade
payloadto 3.90.0 or later - Upgrade
payloadto 4.0.0-canary.34 or later
- Upgrade