CVE-2026-55603
HIGHDescription
http-proxy-middleware is node.js http-proxy middleware. From 3.0.4 until 3.0.7 and 4.1.1, fixRequestBody() is the library's documented helper for re-emitting a request body that was already consumed by a body parser. When the outgoing Content-Type is multipart/form-data, it rebuilds the body with handlerFormDataBodyData(), which interpolates each req.body key and value directly into the multipart wire format without neutralizing CR/LF. A \r\n inside a value (or key) lets an attacker close the current part and inject an entirely new form part. Because the proxy's own body parser saw a single opaque value, any gateway-side policy or validation performed on req.body is evaluated against a different set of fields than the upstream backend ultimately parses a request/parameter desynchronization across the trust boundary. This vulnerability is fixed in 3.0.7 and 4.1.1.
How to fix
This vulnerability affects an unusually large number of packages. The highest-confidence fixes are shown above; the full list is longer. Check the referenced advisories for complete coverage.
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 21% of all known CVEs.
References
Related Vulnerabilities
Other CWE-93 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2025-61884 | High | 7.5 | 98% | KEV + Ransom | - |
| CVE-2022-0666 | High | 7.5 | 44% | - | Fix |
| CVE-2016-3115 | Medium | 6.4 | 37% | - | Fix |
| CVE-2024-20337 | High | 8.2 | 30% | - | Fix |
| CVE-2021-39172 | High | 8.8 | 29% | - | Fix |
| CVE-2016-4975 | Medium | 6.1 | 20% | - | Fix |
Common questions
How do I fix CVE-2026-55603?
Published advisories record a fix for 20 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2026-55603 being actively exploited?
Not that we know of. CVE-2026-55603 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.29% is the estimated probability that it will be exploited in the next 30 days. That is higher than 21% of all scored CVEs.
How severe is CVE-2026-55603?
CVE-2026-55603 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-55603 affect?
Published advisories record a fix for registry.redhat.io/mta/mta (Red Hat / RHEL), registry.redhat.io/mta/mta (Rocky), registry.redhat.io/mta/mta-analyzer (Red Hat / RHEL), registry.redhat.io/mta/mta-analyzer (Rocky), and 16 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-55603
Markdown
[](https://tridentstack.com/cve/CVE-2026-55603)HTML
<a href="https://tridentstack.com/cve/CVE-2026-55603"><img src="https://tridentstack.com/cve/badge/CVE-2026-55603.svg" alt="CVE-2026-55603"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-06-24.