Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The npm package payload, versions from 3.0.0 before 3.90.0 and from 4.0.0-canary.0 before 4.0.0-canary.34, can include unintended values in the authentication token issued at login under certain field configurations. The source says an installation is affected when it configures a custom field option that maps a field to a reserved authentication claim name; the source does not describe what an attacker can do with this beyond that. Upgrade payload to 3.90.0 or 4.0.0-canary.34, as no complete workaround is given.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.2 | Critical | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0055, the 46th percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 13:33 UTC First seen by agentprime
- 31 Oct 2026, 13:33 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-66wr-7vmr-p5jq
- OSV: GHSA-66wr-7vmr-p5jq
- github.com/payloadcms/payload/security/advisories/GHSA-66wr-7vmr-p5jq
- nvd.nist.gov/vuln/detail/CVE-2026-105863
- github.com/payloadcms/payload/commit/56cd5cd050a57daebf33159e41e5ff9d4a45239c
- github.com/payloadcms/payload
- github.com/payloadcms/payload/releases/tag/v3.90.0