Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm
Not in CISA KEV

Payload: ReDoS in Multipart Content-Type ValidationGHSA-2g7p-5934-q4w7

Fix: payloadcms/payload@0084bd5

GHSA-2g7p-5934-q4w7 is a Uncontrolled Resource Consumption vulnerability in payload. A fix is available for payload — see the affected versions and patch details below.

Also known asCVE-2026-105854
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Oct 17, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-2g7p-5934-q4w7.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs28th percentile — riskier than 28% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

114other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
payloadnpm
1.0Mdownloads / week

Description

Payload is a free and open source headless content management system. In versions from 3.0.0 before 3.90.0 and canary versions before 4.0.0-canary.34, a malformed multipart request body can cause multipart Content-Type processing to take an extremely long time, resulting in uncontrolled resource consumption. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmpayload≥ 3.0.0&&< 3.90.03.90.0npm install payload@3.90.0
📦npmpayload≥ 4.0.0-canary.0&&< 4.0.0-canary.344.0.0-canary.34npm install payload@4.0.0-canary.34

Affected Products

1 product · 35 configurations
Application
payloadpayloadcms
≥ 3.0.0 && < 3.90.0
1 version
4.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for payload, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update payload to 3.90.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g7p-5934-q4w7 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

## Impact A malformed multipart request body could take an extremely long time to finish. ## Patches Users should upgrade Payload packages to `>= 3.90.0` or `>= 4.0.0-canary.34`.
O3 Security · Impact-Aware SCA

Is GHSA-2g7p-5934-q4w7 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works
Payload: ReDoS in Multipart Content-Type Validation