CVE-2026-105859

Payload: Unauthorized update to collection documents

An attacker can submit a request to a specific endpoint that permits collection documents to be updated regardless of access control and field level access control.

You are affected if:

• You are configuring orderable: true with any collection or join field.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-105859 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.90.0, 4.0.0-canary.34); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

In the patched version access control is properly enforced.

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

1. What is CVE-2026-105859? CVE-2026-105859 is a critical-severity missing authorization vulnerability in payload (npm), affecting versions < 3.90.0. It is fixed in 3.90.0, 4.0.0-canary.34. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-105859? CVE-2026-105859 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of payload are affected by CVE-2026-105859? payload (npm) versions < 3.90.0 is affected.
4. Is there a fix for CVE-2026-105859? Yes. CVE-2026-105859 is fixed in 3.90.0, 4.0.0-canary.34. Upgrade to this version or later.
5. Is CVE-2026-105859 exploitable, and should I be worried? Whether CVE-2026-105859 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
6. What actually determines whether CVE-2026-105859 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.
7. How do I fix CVE-2026-105859?
   • Upgrade payload to 3.90.0 or later
   • Upgrade payload to 4.0.0-canary.34 or later

Other vulnerabilities in payload