Quick answers
- Is CVE-2026-105805 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105805 being exploited in the wild.
- How severe is CVE-2026-105805?
- 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.88.0; Payload CMS Payload < 3.88.0; >= 4.0.0-canary.0, < 4.0.0-canary.27, before 3.88.0 and canary versions before 4.0.0-canary.27.
- Is there a fix for CVE-2026-105805?
- Yes. payload (npm): upgrade to 3.88.0 or later. Until then: Prevent untrusted users from controlling sort parameters, or restrict their query access to collections without protected fields until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105805 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105805?
- 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.88.0 or later
npm install payload@3.88.0
Prevent untrusted users from controlling sort parameters, or restrict their query access to collections without protected fields until upgrading.
Technical details
The vulnerability is an authorization bypass (CWE-863) in field-level access controls. Payload failed to validate field-level permissions on sort parameters before executing queries, allowing information disclosure (CWE-200) about protected fields. Attack vector is network with no authentication required; the precondition is that the attacker must have general query access to a collection and be able to control sort parameters.
Affected products
- Payload CMS Payload < 3.88.0; >= 4.0.0-canary.0, < 4.0.0-canary.27
Identifiers
- CVE-2026-105805
- GHSA-9g87-32v6-3c2r
Timeline
- 2026-09-22: disclosed
- 2026-10-06: advisory