MediumGHSA-9gqv-wp59-fq42CVE-2025-32997
http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed
Published 15 Apr 2025 · Updated 10 Sept 2026
Affected packages
- Affected
- >=1.3.0 <2.0.9
- Fixed in
- 2.0.9
Update to the fixed version for your release line, for example:
npm install http-proxy-middleware@2.0.9- Affected
- >=3.0.0 <3.0.5
- Fixed in
- 3.0.5
Update to the fixed version for your release line, for example:
npm install http-proxy-middleware@3.0.5Details
In http-proxy-middleware before 2.0.9 and 3.x before 3.0.5, fixRequestBody proceeds even if bodyParser has failed.
Is GHSA-9gqv-wp59-fq42 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected http-proxy-middleware, and gives you the command that fixes it.
References
- Advisorynvd.nist.gov/vuln/detail/CVE-2025-32997
- Linkgithub.com/chimurai/http-proxy-middleware/pull/1096
- Linkgithub.com/chimurai/http-proxy-middleware/commit/1bdccbeec243850f1d2bb50ea0ff2151e725d67e
- Packagegithub.com/chimurai/http-proxy-middleware
- Linkgithub.com/chimurai/http-proxy-middleware/releases/tag/v2.0.9
- Linkgithub.com/chimurai/http-proxy-middleware/releases/tag/v3.0.5
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.