CVE-2026-105863 Payload authentication token field handling issue

Critical 9.2 Published Updated

Attackers can escalate privileges by mapping custom fields to reserved authentication claims in Payload CMS, requiring a non-default configuration.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-105863?

CVE-2026-105863 is a critical authentication bypass vulnerability in payloadcms payload, published on 6 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-915, CWE-290

Which versions are affected by CVE-2026-105863?

4 open source packages ship an affected version, including payload. It affects 1 product.

PackageAffectedFixed in
payload npmFrom 3.0.03.90.0
payload npmFrom 3.0.03.90.0
payload npmFrom 4.0.0-canary.04.0.0-canary.34
payload npmFrom 4.0.0-canary.04.0.0-canary.34

Products include Payloadcms Payload.

How do I fix CVE-2026-105863?

Upgrade payload to a fixed version for your release line: 3.90.0 or 4.0.0-canary.34.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2026-105863 being exploited?

There is no known exploitation of CVE-2026-105863 in the wild and no public exploit code.

Sources

Also known as GHSA-66wr-7vmr-p5jq.

Is CVE-2026-105863 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free