CVE-2026-105863 · GHSA-66wr-7vmr-p5jq
Payload authentication token field handling issue
- Risk score
- 72/100
- CVSS
- 9.4 v3.1
- Exploit chance (30 days)
- 0.4%
- Published
- 6 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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.
- Affected
- payload (npm) >= 3.0.0, < 3.90.0; payload (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34
- Fix
- Upgrade payload to 3.90.0 or 4.0.0-canary.34 (whichever matches your release line) or later.
- Exploitation
- No known exploitation
Story map
At a glance
@payloadcms/plugin-form-builder: Amber, patch this week. Payload is a free and open source headless content management system. In @payloadcms/plugin-form-builder versions before 3.90.0 and canary versions before 4.0.0-canary.34, an attacker can craft a form submission that executes code remotely on the server. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
The flaws
- CVE-2026-105863: Payload authentication token field handling issue (CVSS 9.4 · EPSS 0%)
- CVE-2026-105857: Payload Form Builder has an RCE issue (CVSS 10.0 · EPSS 0%)
- CVE-2026-105859: Payload: Unauthorized update to collection documents (CVSS 9.8 · EPSS 0%)
- CVE-2026-105858: Payload: Remote Code Execution through first-register (CVSS 8.1 · EPSS 0%)
The fix
Upgrade @payloadcms/plugin-form-builder: 3.90.0 · 4.0.0 or later on your release line
Who is exposed: @payloadcms/plugin-form-builder (npm) < 3.90.0; @payloadcms/plugin-form-builder (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34
Where it stands
- No known exploitation
Connects to
- Same weakness: CWE-290 (CWE-290). 54 other warnings in 30 days
- Same product: Earlier payload warnings. 20 in the last 90 days
Why it is Amber
- CVSS 9.4 critical
- Remotely exploitable without logging in
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| payload | npm | >= 3.0.0, < 3.90.0 | 3.90.0 |
| payload | npm | >= 4.0.0-canary.0, < 4.0.0-canary.34 | 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
- https://github.com/advisories/GHSA-66wr-7vmr-p5jq
Original 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.
Last activity 6 Oct 2026. Patch Forecast updates every hour.