---
title: "GHSA-9gqv-wp59-fq42: http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed"
description: "Moderate severity. http-proxy-middleware allows fixRequestBody to proceed even if bodyParser has failed. Affects http-proxy-middleware; fixed in 3.0.5."
url: https://inlinr.com/advisories/GHSA-9gqv-wp59-fq42
lang: en
---

[Packages](https://inlinr.com/packages) / [http-proxy-middleware](https://inlinr.com/packages/http-proxy-middleware) / [Security](https://inlinr.com/packages/http-proxy-middleware/security)

Moderate Vulnerability GHSA-9gqv-wp59-fq42 CVE-2025-32997 Published 15 Apr 2025

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

Your version 

Affected releases · [http-proxy-middleware](https://inlinr.com/packages/http-proxy-middleware)

- 3.x 3.0.0 – 3.0.4 Fixed in 3.0.5
- 2.x 2.0.0 – 2.0.8 Fixed in 2.0.9
- 1.x 1.3.0 – 1.3.1 No fix on this line yet

On 3.x, the newest line:

```
npm install http-proxy-middleware@3.0.5
```

Every release on a timeline

4.x 

1. Not affected

4.0.0 – 4.2.2  
6 releases, latest

3.x 

1. Affected

3.0.0 – 3.0.4  
5 releases
2. Fixed

3.0.5 – 3.0.11  
5 releases

2.x 

1. Affected

2.0.0 – 2.0.8  
9 releases
2. Fixed

2.0.9 – 2.0.12  
4 releases

1.x 

1. Not affected

1.0.0 – 1.2.1  
12 releases
2. Affected

1.3.0 – 1.3.1  
2 releases

82 stable releases of http-proxy-middleware, oldest to newest, one row per major.

## What happens

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

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: none
- **Integrity**: low
- **Availability**: none

CVSS:3.1/​AV:N/​AC:H/​PR:N/​UI:N/​S:C/​C:N/​I:L/​A:N

## References

- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2025-32997 "https://nvd.nist.gov/vuln/detail/CVE-2025-32997")  
nvd.nist.gov/vuln/detail/CVE-2025-32997
- [Pull request](https://github.com/chimurai/http-proxy-middleware/pull/1096 "https://github.com/chimurai/http-proxy-middleware/pull/1096")  
#1096
- [Fix commit](https://github.com/chimurai/http-proxy-middleware/commit/1bdccbeec243850f1d2bb50ea0ff2151e725d67e "https://github.com/chimurai/http-proxy-middleware/commit/1bdccbeec243850f1d2bb50ea0ff2151e725d67e")  
1bdccbe
- [Package](https://github.com/chimurai/http-proxy-middleware "https://github.com/chimurai/http-proxy-middleware")  
github.com/chimurai/http-proxy-middleware
- [Reference](https://github.com/chimurai/http-proxy-middleware/releases/tag/v2.0.9 "https://github.com/chimurai/http-proxy-middleware/releases/tag/v2.0.9")  
github.com/chimurai/http-proxy-middleware/relea…
- [Reference](https://github.com/chimurai/http-proxy-middleware/releases/tag/v3.0.5 "https://github.com/chimurai/http-proxy-middleware/releases/tag/v3.0.5")  
github.com/chimurai/http-proxy-middleware/relea…

A whole project to check? Paste its package.json in the [dependency check](https://inlinr.com/tools/dependency-check): every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.
