All vulnerabilities
CVE-2026-105865GHSA-p223-2wr2-j562

Payload: Incomplete validation during the upload file lifecycle

payloadcms payloadnpmLibraries & packages
Open in ThreatlineRecord JSON
CVSS
8.1High
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.38%Chance of exploitation activity in the next 30 days, higher than 30% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in3.90.0Also 4.0.0-canary.34GitHub
Published6 Oct 2026Updated 7 Oct 2026CVE List

What fixes it

  • 3.90.0payload, npmGitHubnpm install payload@3.90.0
  • 4.0.0-canary.34payload, npmGitHubnpm install payload@4.0.0-canary.34

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

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.

Text from GitHub Advisory Database

Affected versions 6

  • payload, npm< 3.90.0GitHub
  • payload, npm>= 4.0.0-canary.0, < 4.0.0-canary.34GitHub
  • payloadaffected: < 3.90.0CVE List
  • payloadaffected: >= 4.0.0-canary.0, < 4.0.0-canary.34CVE List
  • payload, npmfrom first release, fixed in 3.90.0OSV
  • payload, npmfrom 4.0.0-canary.0, fixed in 4.0.0-canary.34OSV

References 5