CVE-2026-105861: Payload external upload trust validation issue
Impact
Under certain external upload configurations, Payload could send authentication data to a destination that was not verified as trusted. If the affected request contained a valid session, this could expose that session to an unintended recipient.
You are affected if:
- You have enabled external URL-based upload retrieval, where authenticated requests can trigger it.
Patches
Payload now validates the destination before forwarding authentication data and reapplies that validation when a request changes destination.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds It is recommended to update all Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
If you cannot, a valid workaround exists: - Disable external URL-based upload retrieval where practical. - If you cannot disable it, configure the upload header filter to remove authentication data from outbound file requests. - Restrict access to the affected upload functionality.
Other sources
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.
— NVD
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
npm/payloadto a version that resolves this vulnerability.Fixed in 4.0.0-canary.34 - Upgrade
Upgrade
npm/payloadto a version that resolves this vulnerability.Fixed in 3.90.0 - Upgrade
Upgrade
Payloadto a version that resolves this vulnerability.Fixed in 3.90.0 - Configuration
Disable external URL-based upload retrieval where practical.
Payload external URL-based upload retrieval = disabled - Configuration
Configure the upload header filter to remove authentication data from outbound file requests.
Payload upload header filter = remove authentication data - Compensating control
Restrict access to the affected upload functionality.
Event History
Frequently Asked Questions
Which deployments are affected?
Payload versions after 3.0.0 and before 3.90.0 are affected. Version 3.90.0 fixes the issue.
What does an attacker need to exploit this issue?
Exploitation involves an authenticated external URL-based upload retrieval and a redirect to a destination that has not been verified as trusted. The issue can cause authentication data, including a valid session, to be forwarded to that redirected destination.
Who is most exposed?
Deployments that permit authenticated users to retrieve uploads from external URLs are exposed to this behavior. The provided information does not state whether this functionality is enabled by default.
What should be done if patching is not immediately possible?
The provided information identifies the risky condition as external URL-based upload retrieval that follows redirects to destinations not verified as trusted. Until upgrading, restrict or avoid that workflow where operationally possible and review its handling of redirected URLs.