CVE-2026-105863: critical vulnerability in payloadcms payload
Payload authentication token field handling issue
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.2epss 0.5%
from disclosure to weapon27 days
Published on NVDOct 6
1st PoC+27d
Payload is a free and open source headless content management system. In versions after 3.0.0 and before 3.90.0, a custom field option that maps a field to a reserved authentication claim name can place unintended values in the authentication token issued at login. This issue is fixed in version 3.90.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
Affected products
payloadcms · payloadpublic PoCs found — 1
githubgithub.com/lelaboratoiredegenie/CVE-2026-105863★ 0⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.
Related CVEs — payloadcms payload
In the same product, most dangerous first.
CVE-2026-25544CRITICALPayload has an SQL Injection in JSON/RichText Queries on PostgreSQL/SQLite AdaptersEPSS 0.8%CVE-2026-105844CRITICALPayload: Prototype pollution in Payload Import Export pluginEPSS 0.7%CVE-2026-105857CRITICALPayload: RCE in Payload Form BuilderEPSS 0.6%CVE-2023-30843HIGHPayload's hidden fields can be leaked on readable collectionsEPSS 0.6%CVE-2026-105858HIGHPayload: Remote Code Execution through first-registerEPSS 0.5%CVE-2026-105845CRITICALPayload: SQL Injection in SQLite and PostgresEPSS 0.4%