Payload authentication token field handling issue

### 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 Code Location: https://github.com/payloadcms/payload Affected Packages: - npm:payload, affected >= 3.0.0, < 3.90.0, patched in 3.90.0 - npm:payload, affected >= 4.0.0-canary.0, < 4.0.0-canary.34, patched in 4.0.0-canary.34 CWEs: - CWE-290: Authentication Bypass by Spoofing - CWE-915: Improperly Controlled Modification of Dynamically-Determined Object Attributes CVSS: - CVSS_V4: score 9.2, 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 References: - 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 - https://github.com/advisories/GHSA-66wr-7vmr-p5jq