CVE-2026-105865: Payload: Incomplete validation during the upload file lifecycle

Published Oct 6, 2026
·
Updated

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

38 affected componentsFixes available
Payload Payload CMS<3.90.0, <4.0.0-canary.34
npm/payload>=4.0.0-canary.0<4.0.0-canary.34
4.0.0-canary.34
npm/payload<3.90.0
3.90.0
PayloadCMS Payload Node.js<3.90.0
PayloadCMS Payload Node.js=4.0.0-canary0
PayloadCMS Payload Node.js=4.0.0-canary1
PayloadCMS Payload Node.js=4.0.0-canary10
PayloadCMS Payload Node.js=4.0.0-canary11
PayloadCMS Payload Node.js=4.0.0-canary12
PayloadCMS Payload Node.js=4.0.0-canary13
PayloadCMS Payload Node.js=4.0.0-canary14
PayloadCMS Payload Node.js=4.0.0-canary15
PayloadCMS Payload Node.js=4.0.0-canary16
PayloadCMS Payload Node.js=4.0.0-canary17
PayloadCMS Payload Node.js=4.0.0-canary18
PayloadCMS Payload Node.js=4.0.0-canary19
PayloadCMS Payload Node.js=4.0.0-canary2
PayloadCMS Payload Node.js=4.0.0-canary20
PayloadCMS Payload Node.js=4.0.0-canary21
PayloadCMS Payload Node.js=4.0.0-canary22
PayloadCMS Payload Node.js=4.0.0-canary23
PayloadCMS Payload Node.js=4.0.0-canary24
PayloadCMS Payload Node.js=4.0.0-canary25
PayloadCMS Payload Node.js=4.0.0-canary26
PayloadCMS Payload Node.js=4.0.0-canary27
PayloadCMS Payload Node.js=4.0.0-canary28
PayloadCMS Payload Node.js=4.0.0-canary29
PayloadCMS Payload Node.js=4.0.0-canary3
PayloadCMS Payload Node.js=4.0.0-canary30
PayloadCMS Payload Node.js=4.0.0-canary31
PayloadCMS Payload Node.js=4.0.0-canary32
PayloadCMS Payload Node.js=4.0.0-canary33
PayloadCMS Payload Node.js=4.0.0-canary4
PayloadCMS Payload Node.js=4.0.0-canary5
PayloadCMS Payload Node.js=4.0.0-canary6
PayloadCMS Payload Node.js=4.0.0-canary7
PayloadCMS Payload Node.js=4.0.0-canary8
PayloadCMS Payload Node.js=4.0.0-canary9

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  2. Upgrade

    Upgrade npm/payload to a version that resolves this vulnerability.

    Fixed in 3.90.0
  3. Upgrade

    Upgrade Payload to a version that resolves this vulnerability.

    Fixed in 3.90.0
  4. Upgrade

    Upgrade Payload to a version that resolves this vulnerability.

    Fixed in 4.0.0-canary.34
  5. Configuration

    Restrict upload update and deletion operations to trusted users.

    Payload upload collections Upload update and deletion permissions = Trusted users only
  6. 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

Oct 6, 2026
CVE Published
via MITRE·04:45 PM
Data Sourced
via MITRE·04:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 7, 2026
Advisory Published
via GitHub·08:29 PM
Data Sourced
via GitHub·08:29 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203