chimurai
http-proxy-middleware
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
Official registry publication history is available at http-proxy-middleware, but registry activity is not a publisher support boundary.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-55603 | 22 Jun 2026 | >= 3.0.4, < 3.0.7; >= 4.0.0, < 4.1.1 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-55602 | 22 Jun 2026 | >= 4.0.0, < 4.1.0; >= 3.0.0, < 3.0.6; >= 0.16.0, < 2.0.10 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-32997 | 15 Apr 2025 | < 2.0.9; 3.0.0 < 3.0.5 | For more about Red Hat Developer Hub, see References links | Update reference ↗ |
| CVE-2025-32996 | 15 Apr 2025 | < 2.0.8; 3.0.0 < 3.0.4 | For more about Red Hat Developer Hub, see References links | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.