CVE-2026-105861 Payload external upload trust validation issue

High 7.2 Published Updated

Authenticated users can expose session data to unintended recipients via unverified external URL uploads in Payload CMS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2026-105861?

CVE-2026-105861 is a high-severity server-side request forgery vulnerability in payloadcms payload, published on 6 Oct 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

Official description

Payload is a free and open source headless content management system. In versions after 3.0.0 and before 3.90.0, authenticated external URL-based upload retrieval can forward authentication data to a redirected destination that was not verified as trusted, potentially exposing a valid session to an unintended recipient. This issue is fixed in version 3.90.0.

Weakness: CWE-346, CWE-200

Which versions are affected by CVE-2026-105861?

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-105861?

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

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-105861 being exploited?

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

Sources

Also known as GHSA-pj5h-5q6c-3pfx.

Is CVE-2026-105861 in your software?

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

Check your SBOMs for free