Quick answers
- Is CVE-2026-105853 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105853 being exploited in the wild.
- How severe is CVE-2026-105853?
- 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 >= 3.0.0, < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34.
- Is there a fix for CVE-2026-105853?
- 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-105853 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105853?
- Check whether you run payload (npm) or 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
A field access control bypass in Payload's authentication response handlers allows hidden or read-restricted fields to be returned to users lacking permission to view them. The vulnerability affects token refresh and password reset endpoints when an authentication collection defines field-level access restrictions. An authenticated attacker can exploit this via network requests to the affected endpoints with low complexity, gaining unauthorized access to confidential user fields server-side filtering now applies before responses are sent.
Affected products
- Payload Payload >= 3.0.0, < 3.90.0; >= 4.0.0-canary.0, < 4.0.0-canary.34
Identifiers
- CVE-2026-105853
- GHSA-xgv3-crq2-6f69
Timeline
- 2026-09-18: disclosed
- 2026-10-06: advisory
- 2026-09-18: patched