Summary
Payload authentication token field handling issue
Advisory details
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.
References
- https://github.com/advisories/GHSA-66wr-7vmr-p5jq
- https://github.com/payloadcms/payload/security/advisories/GHSA-66wr-7vmr-p5jq
- https://nvd.nist.gov/vuln/detail/CVE-2026-105863
- https://github.com/payloadcms/payload/commit/56cd5cd050a57daebf33159e41e5ff9d4a45239c
- https://github.com/payloadcms/payload/releases/tag/v3.90.0
Related vulnerabilities
All Supply chain →- HIGHCVE-2026-70179
Microsoft Security Advisory CVE-2026-70179 - ASP.NET Core Elevation of Privilege Vulnerability
- HIGHCVE-2026-62367
Vikunja: OIDC email-fallback account linking ignores email_verified, enabling local-account takeover
- MEDIUMGHSA-9q47-3cm2-2rp8
pyLoad: Rate-Limit Bypass and Audit-Log Spoofing via Trusted Client-Controlled `X-Forwarded-For` Header
- HIGHCVE-2026-104891
mppx-condition-gate: Free-access path grants on a self-declared wallet without proving control
- HIGHCVE-2026-106100
Payload: Field-level write access bypass in Payload on MongoDB
- HIGHCVE-2026-105741
Langflow: IP Spoofing Bypass via `X-Forwarded-For` Allowing Remote Configuration Write