Quick answers
- Is CVE-2026-105851 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105851 being exploited in the wild.
- How severe is CVE-2026-105851?
- Critical severity, published 6 October 2026.
- Which products and versions are affected?
- Payload CMS Payload >3.0.0, <3.90.0 and >4.0.0-canary.0, <4.0.0-canary.34.
- Is there a fix for CVE-2026-105851?
- Yes: fixed in 3.90.0, 4.0.0-canary.34. Until then: Add a beforeDuplicate field hook to restricted fields and set the value to empty or a default value until upgrading. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105851 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-105851?
- Check whether you run 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
- Fixed in: 3.90.0, 4.0.0-canary.34
Add a beforeDuplicate field hook to restricted fields and set the value to empty or a default value until upgrading.
Technical details
The duplicate operation in Payload copies field values from source documents without respecting access.read or access.create rules or field visibility settings. An unauthenticated or low-privilege attacker can exploit this via a network request to duplicate a document and retrieve restricted field contents. The disableDuplicate setting on auth collections does not prevent this bypass.
Affected products
- Payload CMS Payload >3.0.0, <3.90.0 and >4.0.0-canary.0, <4.0.0-canary.34
Identifiers
- CVE-2026-105851
- GHSA-vc4h-q48j-5hcx
Timeline
- 2026-09-18: disclosed: Published to GitHub Advisory Database
- 2026-10-06: advisory: Updated advisory