Is http-proxy-middleware 0.16 vulnerable?
npm · 1 release from 0.16.0 to 0.16.0 · latest http-proxy-middleware is 4.2.1 · checked 1 Nov 2026
Yes: 2 known advisories
Yes. http-proxy-middleware 0.16.0, the last 0.16 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2024-21536, CVE-2026-55602. Upgrade to 2.0.10 or later to fix all of them.
npm install http-proxy-middleware@2.0.10Advisories affecting http-proxy-middleware 0.16.0
http-proxy-middleware `router` host+path substring matching allows Host-header-driven backend routing bypass
- Affected
- >=3.0.0 <3.0.6 · >=4.0.0 <4.1.0 · >=0.16.0 <2.0.10
- Fixed in
- 2.0.10, 3.0.6, 4.1.0
Denial of service in http-proxy-middleware
- Affected
- <2.0.7 · >=3.0.0 <3.0.3
- Fixed in
- 2.0.7, 3.0.3
Which of your client projects are still on http-proxy-middleware 0.16?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact http-proxy-middleware version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other http-proxy-middleware versions
- http-proxy-middleware 0.19
- http-proxy-middleware 0.18
- http-proxy-middleware 0.17
- http-proxy-middleware 0.15
- http-proxy-middleware 0.14
- http-proxy-middleware 0.13
- http-proxy-middleware 4.2
- http-proxy-middleware 4.1
- http-proxy-middleware 4.0
- http-proxy-middleware 3.0
- http-proxy-middleware 2.0
- All http-proxy-middleware advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.