Skip to content
Fencer Vulns
medium 4.0

CVE-2025-32996 json

http-proxy-middleware can call writeBody twice because "else if" is not used

published 2025-04-15 18 mo ago modified 2026-09-10 1 mo ago also EUVD-2025-11356 , GHSA-4www-5p9h-95mh

cvss
4.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

In http-proxy-middleware before 2.0.8 and 3.x before 3.0.4, writeBody can be called twice because "else if" is not used.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-32996 updated cvss 4.0

http-proxy-middleware: Always-Incorrect Control Flow Implementation in http-proxy-middleware

  • Red Hat Cryostat 3 io.cryostat-cryostat3 Red Hat Cryostat 4 io.cryostat-cryostat Red Hat Migration Toolkit for Applications 7 mta/mta-ui-rhel9 Red Hat Network Observability Operator network-observability/network-observability-console-plugin-rhel9 Red Hat OpenShift Lightspeed openshift-lightspeed-tech-preview/lightspeed-console-plugin-rhel9 Red Hat OpenShift Serverless openshift-serverless-1/kn-backstage-plugins-eventmesh-rhel8
    +14 more products
    Red Hat Ansible Automation Platform 2 lightspeed-rhel8, automation-gateway, automation-controller, automation-eda-controller, ansible-automation-platform-25/lightspeed-rhel8, ansible-automation-platform-26/lightspeed-rhel9 Red Hat build of Apache Camel - HawtIO 4 io.hawt-project Red Hat build of Apicurio Registry 2 io.apicurio-apicurio-registry Red Hat build of OptaPlanner 8 org.optaweb.vehiclerouting-optaweb-vehicle-routing Red Hat Data Grid 8 org.infinispan-infinispan-console Red Hat Enterprise Linux 8 pcs, pcs-snmp Red Hat Enterprise Linux 9 pcs, pcs-snmp Red Hat Fuse 7 io.apicurio-apicurito, io.syndesis-syndesis-parent Red Hat Integration Camel K 1 io.apicurio-apicurio-registry Red Hat OpenShift AI (RHOAI) rhoai/odh-dashboard-rhel8, rhoai/odh-ml-pipelines-driver-rhel8, rhoai/odh-ml-pipelines-launcher-rhel8, rhoai/odh-ml-pipelines-api-server-v2-rhel8, rhoai/odh-ml-pipelines-persistenceagent-v2-rhel8, rhoai/odh-ml-pipelines-scheduledworkflow-v2-rhel8, +2 more Red Hat OpenShift distributed tracing 3 rhosdt/tempo-rhel8, rhosdt/tempo-query-rhel8, rhosdt/tempo-gateway-rhel8, rhosdt/tempo-rhel8-operator, rhosdt/tempo-gateway-opa-rhel8, rhosdt/tempo-jaeger-query-rhel8 Red Hat Process Automation 7 org.uberfire-uberfire-parent Red Hat Quay 3 quay/quay-rhel8 Red Hat Trusted Profile Analyzer rhtpa/rhtpa-trustification-service-rhel9
    affected: workaround, no fix available “Fix deferred”
  • Red Hat Developer Hub 1.6 rhdh 1.6.2-1750887220
    fixed: vendor fix RHSA-2025:9966
  • Red Hat Developer Hub 1.7 rhdh 1.7.0-1754936470
    fixed: vendor fix RHSA-2025:14090
  • Red Hat Developer Hub 1.6 rhdh 1.6.2-1750886883, rhdh 1.6.2-1750938107 Red Hat Developer Hub 1.7 rhdh 1.7.0-1754935808, rhdh 1.7.0-1754942441
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

0.47% chance of exploitation in the next 30 days, higher than 41% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 4.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L
GitHub 3.1 4.0 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:N/A:L
NVD 3.1 5.3 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
npm http-proxy-middleware
>=1.3.0, <2.0.8
>=3.0.0, <3.0.4
2.0.8
3.0.4

Affected products

  • chimurai http-proxy-middleware

Classification

Weakness
  • CWE-670 Always-Incorrect Control Flow Implementation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.