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

CVE-2025-32997

MEDIUM

CVE-2025-32997 is a medium-severity (CVSS 4) CWE-754 vulnerability in http-proxy-middleware. O3 Security confirms whether CVE-2025-32997 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed

Also known asGHSA-9gqv-wp59-fq42
Published
Apr 15, 2025
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

http-proxy-middlewarenpm
26.5Mdownloads / week

Description

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

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
📦npmhttp-proxy-middleware1.3.0&&< 2.0.92.0.9
📦npmhttp-proxy-middleware3.0.0&&< 3.0.53.0.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for http-proxy-middleware. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update http-proxy-middleware to 2.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32997 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-32997 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-32997. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In http-proxy-middleware before 2.0.9 and 3.x before 3.0.5, fixRequestBody proceeds even if bodyParser has failed.
O3 Security · Impact-Aware SCA

Is CVE-2025-32997 in your dependencies?

O3 detects CVE-2025-32997 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.