Disclosure summary
### Impact Under certain field configurations, Payload could include unintended values in the authentication token issued at login. You are affected if: - You use an affected Payload version and have configured a custom field option that maps a field to a reserved authentication claim name. ### Patches Payload now restricts which field configuration options can influence the contents of the authentication token. Users should upgrade payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`. ### Workarounds There is no complete workaround. Users should upgrade payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
Source-specific records & product guidance
Sources retain their own attribution and scoring. Follow the original record to confirm affected versions, fixed releases, and configuration conditions.
GitHub Reviewed Security Advisories · GHSA-66wr-7vmr-p5jq
Open original source · Updated Oct 07, 2026
Payload authentication token field handling issue
Source severity: CRITICAL / 9.2
| Ecosystem | Package | Affected range | First patched |
|---|---|---|---|
| npm | payload | >= 3.0.0, < 3.90.0 | 3.90.0 |
| npm | payload | >= 4.0.0-canary.0, < 4.0.0-canary.34 | 4.0.0-canary.34 |
Original records & references
- NIST NVD record
- CVE Program record
- github.com — Reviewed advisory
PUBLISHED 2026-10-07T16:28:18-04:00
MODIFIED 2026-10-07T16:28:19-04:00
INGESTED 2026-10-08T12:30:39-04:00