Check out the latest research from IONIX: NEW! State of the WAF Report

New CVE Detected

CVE-2026-105854 – Denial of Service (ReDoS) – Payload CMS 3.0.0–3.89.x and 4.0.0-canary.0–4.0.0-cana

Be the first to know when new zero-days emerge:

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-Type processing uses an inefficient regular expression to validate the presence of valid multipart parameters (CWE-1333: Inefficient Regular Expression Complexity).
  • Trigger conditions: When the Content-Type header 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-Type header 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-Type validation.
  • 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-Type headers on multipart requests, and apply request timeouts/rate limiting to reduce the impact of long-running requests until the upgrade can be completed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge