Summary
CVE-2026-105854 is a Regular Expression Denial of Service (ReDoS) vulnerability in Payload CMS’s multipart request handling. An attacker can send a specially malformed multipart Content-Type header to cause the server’s validation logic to enter catastrophic backtracking, consuming excessive CPU and resulting in uncontrolled resource consumption. The flaw carries a CVSS score of 8.7 (High) and requires no authentication or user interaction to exploit.
Technical details
- Root cause: Payload’s multipart
Content-Typeprocessing uses an inefficient regular expression to validate the presence of valid multipart parameters (CWE-1333: Inefficient Regular Expression Complexity). - Trigger conditions: When the
Content-Typeheader deviates slightly from the expected multipart format near the end of the string, the underlying JavaScript (V8) regex engine falls into catastrophic backtracking while evaluating the pattern. - Attack vector: Network — a single malformed HTTP request with a crafted multipart
Content-Typeheader is sufficient; no authentication, prior session, or user interaction is required. - Impact: Uncontrolled resource consumption (CWE-400) causing the request-handling thread/process to hang, leading to denial of service for the affected Payload CMS instance. There is no confidentiality or integrity impact — only availability is affected.
Affected software
- Payload CMS (npm package
payload) versions >= 3.0.0 and < 3.90.0 - Payload CMS versions >= 4.0.0-canary.0 and < 4.0.0-canary.34
Severity
- CVSS v4.0 Base Score: 8.7 (High)
- Vector:
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
Mitigation and recommended actions
- Immediate: Upgrade Payload CMS to version 3.90.0 (for 3.x deployments) or 4.0.0-canary.34 (for 4.x canary deployments) or later, which contain the fix for the inefficient multipart
Content-Typevalidation. - If immediate patching is not possible: Place a reverse proxy or web application firewall in front of the Payload CMS instance to inspect and reject malformed or anomalous
Content-Typeheaders on multipart requests, and apply request timeouts/rate limiting to reduce the impact of long-running requests until the upgrade can be completed.

