CVE-2025-32997

In http-proxy-middleware before 2.0.9 and 3.x before 3.0.5, fixRequestBody proceeds even if bodyParser has failed.

Published: 2025-04-15 Last update: 2025-10-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-32997 is rated Low Risk (27/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.39%). 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-2025-32997

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-06-15 0.08% 0.39% +0.31%
2 2026-02-09 0.02% 0.08% +0.06%
3 2026-01-18 — 0.02% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-32997

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.0 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N 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:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
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:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 2.2 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N 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:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2025-32997

GitHub Security Advisory for CVE-2025-32997

GHSA-9gqv-wp59-fq42 · Severity: medium · Ecosystem: npm — http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed

OS Trackers for CVE-2025-32997

vendor priority summary link
redhat medium — https://access.redhat.com/security/cve/CVE-2025-32997

Affected software / configurations for CVE-2025-32997

Vendor Product Version Raw CPE
chimurai http-proxy-middleware < 2.0.9 cpe:2.3:a:chimurai:http-proxy-middleware:*:*:*:*:*:*:*:*
chimurai http-proxy-middleware >= 3.0.0, < 3.0.5 cpe:2.3:a:chimurai:http-proxy-middleware:*:*:*:*:*:*:*:*

References for CVE-2025-32997

cvelogic Threat Intelligence