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.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-105861US | high8.2 | — | ||
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 authe… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/payloadcms/payloadPACKAGE
- https://github.com/payloadcms/payload/commit/ba5cf6ae20d27a2c15106cb37466419031f86e6dWEB
- https://github.com/payloadcms/payload/releases/tag/v3.90.0WEB
- https://github.com/payloadcms/payload/security/advisories/GHSA-pj5h-5q6c-3pfxWEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-105861ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan