cve.bz

CVE-2026-105865 payloadcms payload: Path traversal

8.1 highEPSS 0.4%Fix available

High (8.1) in payloadcms payload. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in payload 3.90.0, 4.0.0-canary.34.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 32nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
CWE-73 External Control of File Name or Path
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105865 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105865?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105865?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105865 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
payloadcms:payloadbefore 3.90.0
payloadcms:payload4.0.0:canary0
payloadcms:payload4.0.0:canary1
payloadcms:payload4.0.0:canary10
payloadcms:payload4.0.0:canary11
payloadcms:payload4.0.0:canary12
payloadcms:payload4.0.0:canary13
payloadcms:payload4.0.0:canary14
payloadcms:payload4.0.0:canary15
payloadcms:payload4.0.0:canary16
payloadcms:payload4.0.0:canary17
payloadcms:payload4.0.0:canary18
payloadcms:payload4.0.0:canary19
payloadcms:payload4.0.0:canary2
payloadcms:payload4.0.0:canary20
payloadcms:payload4.0.0:canary21
payloadcms:payload4.0.0:canary22
payloadcms:payload4.0.0:canary23
payloadcms:payload4.0.0:canary24
payloadcms:payload4.0.0:canary25
payloadcms:payload4.0.0:canary26
payloadcms:payload4.0.0:canary27
payloadcms:payload4.0.0:canary28
payloadcms:payload4.0.0:canary29
payloadcms:payload4.0.0:canary3
payloadcms:payload4.0.0:canary30
payloadcms:payload4.0.0:canary31
payloadcms:payload4.0.0:canary32
payloadcms:payload4.0.0:canary33
payloadcms:payload4.0.0:canary4
payloadcms:payload4.0.0:canary5
payloadcms:payload4.0.0:canary6
payloadcms:payload4.0.0:canary7
payloadcms:payload4.0.0:canary8
payloadcms:payload4.0.0:canary9

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p223-2wr2-j562npmpayload<3.90.03.90.0
GHSA-p223-2wr2-j562npmpayload>=4.0.0-canary.0 <4.0.0-canary.344.0.0-canary.34

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High
  • CAPEC-13 Subverting Environment Variable Values Likelihood: High · Severity: Very High
  • CAPEC-72 URL Encoding Likelihood: High · Severity: High
  • CAPEC-80 Using UTF-8 Encoding to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-267 Leverage Alternate Encoding Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON