CVE-2026-105863

Payload authentication token field handling issue

Published Oct 6, 2026 CVSS 4.0 · 9.2 Critical EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

Payload CMS permits administrators to define custom fields that can map to authentication claim names. In any release after 3.0.0 and before 3.90.0 a misconfiguration may cause the login‑generated JWT to contain unintended values for reserved claim names. This flaw allows an attacker to forge or alter authentication tokens and obtain unauthorized access or impersonate legitimate users.

Affected Systems

The vulnerability affects Payload CMS versions 3.0.0 through 3.89.99, specifically when custom field mappings target authentication claim names. The impact applies to all deployments using these version ranges, regardless of hosting environment.

Risk and Exploitability

The CVSS score of 9.2 indicates a high severity vulnerability. The EPSS score is not published, and the vulnerability is not listed in CISA KEV, suggesting no current mass exploitation. The likely attack vector is remote via the CMS administrative interface, where an attacker with sufficient privileges can create malicious field mappings that influence the token payload generated at login.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Payload CMS to version 3.90.0 or later to apply the vendor fix.
  • Review all custom field configurations and ensure none map to authentication claim names unless strictly required.
  • Revoke or rotate all existing authentication tokens after the upgrade to prevent the use of compromised tokens.

Generated by OpenCVE AI on October 6, 2026 at 19:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-66wr-7vmr-p5jq Payload authentication token field handling issue
History
Type Values Removed Values Added
CPEs cpe:2.3:a:payloadcms:payload:*:*:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary0:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary10:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary11:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary12:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary13:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary14:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary15:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary16:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary17:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary18:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary19:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary1:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary20:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary21:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary22:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary23:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary24:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary25:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary26:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary27:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary28:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary29:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary2:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary30:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary31:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary32:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary33:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary3:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary4:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary5:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary6:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary7:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary8:*:*:*:node.js:*:*
cpe:2.3:a:payloadcms:payload:4.0.0:canary9:*:*:*:node.js:*:*
Metrics cvssV3_1

{'score': 9.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Payloadcms
Payloadcms payload
Vendors & Products Payloadcms
Payloadcms payload
Type Values Removed Values Added
Description 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.
Title Payload authentication token field handling issue
Weaknesses CWE-290
CWE-915
References
Metrics cvssV4_0

{'score': 9.2, 'vector': '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'}

Weaknesses
  • CWE-290

    Authentication Bypass by Spoofing

  • CWE-915

    Improperly Controlled Modification of Dynamically-Determined Object Attributes

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 9, 2026, 1:15 AM
Reserved
Oct 5, 2026, 11:06 PM
Status
Analyzed
Published
Oct 6, 2026, 5:17 PM
Modified
Oct 15, 2026, 12:09 AM