Is CVE-2026-105847 exploited in the wild?

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

How severe is CVE-2026-105847?

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

Which products and versions are affected?

payload (npm) SEMVER:introduced=3.0.0,fixed=3.90.0; Payload CMS Payload 3.0.0 to 3.89.x; 4.0.0-canary.0 to 4.0.0-canary.33.

How is CVE-2026-105847 attacked?

It is attacked over the network.

Am I affected by CVE-2026-105847?

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-105847: Payload polymorphic join queries information disclosure

CVE-2026-105847 · Severity: high · CVSS 4 · Published 2026-10-06

Payload is a headless CMS and backend framework that manages content collections and user queries. An authenticated user with query access could exploit polymorphic join filters to infer hidden or read-restricted field values, including password-reset tokens. This allows direct exposure of sensitive data that should remain protected from unauthorized access.

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

Quick answers

Is CVE-2026-105847 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105847 being exploited in the wild.
How severe is CVE-2026-105847?: High severity, with a CVSS score of 4, published 6 October 2026.
Which products and versions are affected?: payload (npm) SEMVER:introduced=3.0.0,fixed=3.90.0; Payload CMS Payload 3.0.0 to 3.89.x; 4.0.0-canary.0 to 4.0.0-canary.33.
Is there a fix for CVE-2026-105847?: Yes. payload (npm): upgrade to 3.90.0 or later. Until then: Restricting read access to sensitive collections reduces exposure but does not fully replace upgrading to a patched version. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105847 attacked?: It is attacked over the network.
Am I affected by CVE-2026-105847?: 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
```

Restricting read access to sensitive collections reduces exposure but does not fully replace upgrading to a patched version.

Technical details

The vulnerability is an information disclosure issue (CWE-200, CWE-639) in Payload's polymorphic join query handling. An authenticated attacker with query privileges can craft polymorphic join filters to infer values of hidden or read-restricted fields by observing query behavior, compromising confidentiality without requiring further privileges or user interaction. The attack vector is network-based and affects versions 3.0.0 through 3.89.x and 4.0.0-canary.0 through 4.0.0-canary.33.

Affected products

Payload CMS Payload 3.0.0 to 3.89.x; 4.0.0-canary.0 to 4.0.0-canary.33

Identifiers

CVE-2026-105847
GHSA-fpww-c55p-cjv6

Timeline

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

References

https://github.com/payloadcms/payload/security/advisories/GHSA-fpww-c55p-cjv6

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