Is CVE-2026-105859 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105859 being exploited in the wild.

How severe is CVE-2026-105859?

Critical severity, with a CVSS score of 9.8, published 6 October 2026.

Which products and versions are affected?

payload (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Payload before 3.90.0 and canary versions before 4.0.0-canary.34.

Is there a fix for CVE-2026-105859?

Yes. payload (npm): upgrade to 3.90.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-105859 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-105859?

Check whether you run payload (npm) or Payload CMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105859: Payload CMS access control bypass in reorder endpoint

CVE-2026-105859 · Severity: critical · CVSS 9.8 · Published 2026-10-06

Payload is a headless content management system that allows organizations to manage and deliver content via APIs. An attacker can exploit an update endpoint to modify collection documents without proper permission checks when certain field features are enabled, potentially exposing or altering sensitive data. The vulnerability affects versions before 3.90.0 and canary versions before 4.0.0-canary.34.

Technologies: payload (npm), Payload CMS Payload. Vendors: npm, Payload CMS.

Quick answers

Is CVE-2026-105859 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105859 being exploited in the wild.
How severe is CVE-2026-105859?: Critical severity, with a CVSS score of 9.8, published 6 October 2026.
Which products and versions are affected?: payload (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Payload before 3.90.0 and canary versions before 4.0.0-canary.34.
Is there a fix for CVE-2026-105859?: Yes. payload (npm): upgrade to 3.90.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105859 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-105859?: Check whether you run payload (npm) or Payload CMS Payload at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

payload (npm): upgrade to 3.90.0 or later
```
npm install payload@3.90.0
```

Technical details

The vulnerability exists in the reorder update endpoint which fails to enforce collection-level and field-level access control checks when orderable is enabled on a collection or join field. An authenticated attacker can submit a request to this endpoint to modify document data without authorization. The fix constrains reorder updates to enforce access controls via hasWhereAccessResult and combineQueries functions.

Affected products

Payload CMS Payload before 3.90.0 and canary versions before 4.0.0-canary.34

Identifiers

CVE-2026-105859
GHSA-f7hx-52q9-hcrf

Timeline

2026-10-06: disclosed
2026-09-18: patched: v3.90.0 released

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.