payloadcms payload: critical vulnerability

payloadcms payload

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.

Do this now

Upgrade payload to 3.90.0.

Fix it

payload npm

On 3.x?npm install payload@3.90.0
On 4.xNo stable fix for 4.x yet (only 4.0.0-canary.34)

First seen: 2 Nov 2026
Last update: 2 Nov 2026, 17:18 UTC
Fixed in: payload 4.0.0-canary.34
payload 3.90.0
Identifiers: CVE-2026-105863
CVSS: 9.4
Source: news
On the menu as: npm packages

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## payloadcms payload: critical vulnerability
Severity: critical. Patch status: patched.
Affected: payloadcms payload
Fixed in: payload 4.0.0-canary.34, payload 3.90.0
Ids: CVE-2026-105863

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.

## Steps
1. Search every lockfile and manifest (package-lock.json, yarn.lock, pnpm-lock.yaml, requirements*.txt, poetry.lock, uv.lock, composer.lock, go.sum, Cargo.lock, Gemfile.lock) for `payload`. For each hit, compare the installed version with the fix on the same major line: payload 4.0.0-canary.34, payload 3.90.0. If it's lower, give the exact upgrade command for the package manager this repo uses.

## Fix by release line
| Line | State | Fix | Until then |
|---|---|---|---|
| payload 4.0.x | No stable fix (only rc) | 4.0.0-canary.34 is a prerelease | restrict network access to it |
| payload 3.0.x | fixed | 3.90.0 | — |

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-105863") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://github.com/payloadcms/payload/commit/56cd5cd050a57daebf33159e41e5ff9d4a45239c https://nvd.nist.gov/vuln/detail/CVE-2026-105863
https://pwned.coffee/i/payload-is-a-free-and-open-source-headless-content-manag-cve-2026-105863

Timeline

2 Nov 2026, 17:18 UTC
Fix status: unknown → patched.
2 Nov 2026
First reported.

Receipt

Exploitation: No known exploitation
Checked by hand “Payload's advisory GHSA-66wr-7vmr-p5jq (read 2 Nov 2026): "Users should upgrade payload packages to >= 3.90.0 or >= 4.0.0-canary.34."” source
Fix by release line: Product Affected Fixed in Source
payload (npm) >= 4.0.0-canary.0, < 4.0.0-canary.34 4.0.0-canary.34 Checked by hand checked 3 Nov
payload (npm) >= 3.0.0, < 3.90.0 3.90.0 Checked by hand checked 3 Nov
Score: CVSS 9.4 (critical). CVSS 3.1 9.4 (NVD) for CVE-2026-105863
Last checked: 4 Nov 2026, 08:18 UTC

Product	Affected	Fixed in	Source
payload (npm)	>= 4.0.0-canary.0, < 4.0.0-canary.34	4.0.0-canary.34	Checked by hand checked 3 Nov
payload (npm)	>= 3.0.0, < 3.90.0	3.90.0	Checked by hand checked 3 Nov

Sources: KEV – CVE record ✓ Vendor ✓

Sources

Totalone very hot coffee