CVE-2026-8159 | multiparty vulnerable to ReDoS via filename parsing

[email protected] and lower versions are vulnerable to denial of service via regular expression backtracking in the Content-Disposition filename parameter parser. A crafted multipart upload with a long header value can cause regex matching to take seconds, blocking the event loop. Impact: any service accepting multipart uploads via multiparty is affected. Workarounds: limiting upload sizes at the proxy or gateway layer reduces but does not eliminate the attack surface, since a small header of around 8 KB is sufficient to trigger the vulnerable backtracking. Upgrade to [email protected] or higher.

Published: 2026-05-12 Last update: 2026-05-13 Assigner: ce714d77-add3-4f53-aff5-83d477b104bb Source: ce714d77-add3-4f53-aff5-83d477b104bb

Conclusion & alert: CVE-2026-8159 is rated Low Risk (36/100): CVSS High severity, with low exploitation likelihood (EPSS 0.06%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-8159

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-18 0.04% 0.06% +0.02%
2 2026-05-12 0.04%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-8159

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 ce714d77-add3-4f53-aff5-83d477b104bb

Weakness enumeration for CVE-2026-8159

GitHub Security Advisory for CVE-2026-8159

GHSA-65x3-rw7q-gx94 · Severity: high · Ecosystem: npm — multiparty vulnerable to ReDoS via filename parsing

OS Trackers for CVE-2026-8159

vendor priority summary link
debian not yet assigned CVE-2026-8159 not yet assigned priority: Debian including 1 source packages (node-multiparty), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 3, resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-8159

Affected software / configurations for CVE-2026-8159

Vendor Product Version Raw CPE
pillarjs multiparty < 4.3.0 cpe:2.3:a:pillarjs:multiparty:*:*:*:*:*:node.js:*:*

References for CVE-2026-8159

cvelogic Threat Intelligence