CVE-2026-105865: Payload: Incomplete validation during the upload file lifecycle
Impact Under certain conditions, an authenticated user with permission to modify uploads could cause unintended files to be removed during file cleanup. This may result in data loss or service disruption.
You are affected if: - You use Payload upload collections with local file storage. - Untrusted authenticated users can update or delete uploads.
Deployments that restrict upload management to trusted users are less exposed.
Patches Payload now validates uploaded filenames and ensures file cleanup remains within the configured upload directory.
Users should upgrade Payload packages to >= 3.90.0 or >= 4.0.0-canary.34.
Workarounds Restrict upload update and deletion operations to trusted users and validate submitted filenames. These measures are temporary mitigations. Upgrading to a patched version is recommended.
Other sources
Payload is a free and open source headless content management system. In versions before 3.90.0 and canary versions before 4.0.0-canary.34, an authenticated user who can update or delete uploads stored locally can cause file cleanup to remove unintended files outside the configured upload directory, resulting in data loss or service disruption. Deployments that restrict upload management to trusted users are less exposed. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.
— 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 - Upgrade
Upgrade
Payloadto a version that resolves this vulnerability.Fixed in 4.0.0-canary.34 - Configuration
Restrict upload update and deletion operations to trusted users.
Payload upload collections Upload update and deletion permissions = Trusted users only - Configuration
Validate submitted filenames to prevent file cleanup from affecting files outside the configured upload directory.
Payload upload lifecycle Submitted filename validation = Enabled
Event History
Frequently Asked Questions
Which deployments are most exposed to this issue?
Deployments that store uploads locally and allow authenticated users to update or delete uploads are exposed. Environments that restrict upload management to trusted users are less exposed.
What access does an attacker need?
An attacker needs an authenticated account with permission to update or delete locally stored uploads. No user interaction is required.
What can an attacker do?
They can cause the file-cleanup process to remove unintended files outside the configured upload directory, potentially causing data loss or service disruption.
Which versions contain the fix?
The issue is fixed in Payload CMS 3.90.0 and 4.0.0-canary.34. Versions before 3.90.0 and canary versions before 4.0.0-canary.34 are affected.