Skip to main content
VulnerabilityPublished

CVE-2026-105865: payloadcms payload · Path Traversal

Affects payloadcms payloadSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High : upgrade to 4.0.0-canary.34 or 3.90.0 soon.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.0.0-canary.34, 3.90.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade payload and payloadcms/payload to 4.0.0-canary.34 or 3.90.0.

Affected software

ProductAffectedFixed in
payloadcmspayloadAffected
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 4.0.0-canary.34
payloadcmspayloadAffected
  • <3.90.0
Fixed in
  • 3.90.0
GitHubpayloadcms/payloadpkg:github/payloadcms/payloadOther threatsAffected
  • <3.90.0
  • >=4.0.0-canary.0 <4.0.0-canary.34
Fixed in
  • 3.90.0
  • 4.0.0-canary.34

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to PayloadCMS version 3.90.0 or later, or 4.0.0-canary.34 or later, where the vulnerability is fixed. Restrict upload management permissions to trusted users to reduce exposure until the upgrade can be applied.

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.

References

Community reviews

Loading reviews…