Is CVE-2026-105852 exploited in the wild?

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

How severe is CVE-2026-105852?

Medium severity, with a CVSS score of 4, published 6 October 2026.

Which products and versions are affected?

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

Is there a fix for CVE-2026-105852?

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-105852 attacked?

It is attacked over the network.

Am I affected by CVE-2026-105852?

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-105852: Payload relationship-query authorization bypass

Q: Is there a fix for CVE-2026-105852?

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.

Q: How is CVE-2026-105852 attacked?

It is attacked over the network.

Q: Am I affected by CVE-2026-105852?

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-105852 · Severity: medium · CVSS 4 · Published 2026-10-06

Payload is a headless CMS that manages document collections with access control rules. An authorization bypass flaw allows attackers to query and read protected documents through relationship fields in readable collections, bypassing intended access restrictions. This exposes confidential data that should have been protected by access control constraints.

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

Quick answers

Is CVE-2026-105852 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105852 being exploited in the wild.
How severe is CVE-2026-105852?: Medium severity, with a CVSS score of 4, published 6 October 2026.
Which products and versions are affected?: payload (npm) SEMVER:introduced=0,fixed=3.90.0; Payload CMS Payload < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34.
Is there a fix for CVE-2026-105852?: 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-105852 attacked?: It is attacked over the network.
Am I affected by CVE-2026-105852?: 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 is an authorization bypass (CWE-862) in Payload's relationship-query handling. A readable collection with a relationship to a protected collection fails to enforce access.read constraints when querying related documents, allowing an unauthenticated attacker to retrieve information via network without user interaction. The vulnerability affects versions before 3.90.0 and canary versions before 4.0.0-canary.34.

Affected products

Payload CMS Payload < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34

Identifiers

CVE-2026-105852
GHSA-7c34-32v3-j575

Timeline

2026-09-18: disclosed
2026-10-06: advisory

References

https://github.com/payloadcms/payload/security/advisories/GHSA-7c34-32v3-j575

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