cve.bz

CVE-2026-55603 chimurai http-proxy-middleware: CRLF Injection

7.5 highExploit referenceEPSS 0.3%Fix available

High (7.5) in chimurai http-proxy-middleware. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in http-proxy-middleware 3.0.7, 4.1.1.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:H/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-06-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-93 Improper Neutralization of CRLF Sequences (CRLF Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-55603 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-55603?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-55603?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-55603 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
chimurai:http-proxy-middlewarefrom 3.0.4 before 3.0.7
chimurai:http-proxy-middlewarefrom 4.0.0 before 4.1.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gcq2-9pq2-cxqmnpmhttp-proxy-middleware>=3.0.4 <3.0.73.0.7
GHSA-gcq2-9pq2-cxqmnpmhttp-proxy-middleware>=4.0.0 <4.1.14.1.1

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

Red Hat rates this issue as having Moderate impact for Red Hat products that bundle http-proxy-middleware 3.0.5 in a proxy configuration that re-emits an already-consumed request body via fixRequestBody(). Affected components are tracked via delegated engineering trackers and include Cluster Observability Operator's Prometheus console proxy, the Konflux mintmaker-renovate-image, Migration Toolkit for Applications (MTA) UI, RHTAS console UI, and RHTPA/Trustification service. Red Hat OpenShift AI MLflow images were initially assessed as in-scope but ship http-proxy-middleware 1.3.1/2.0.6, both outside the vulnerable ranges (>= 3.0.4, < 3.0.7 and >= 4.0.0, < 4.1.1), and are not affected. Other Red Hat products either do not bundle an affected http-proxy-middleware version or do not expose the vulnerable code path in normal operation.

Red Hat's mitigation

Restrict network access to affected proxy services. Do not pass untrusted user input into proxy target or header configuration. Upgrade http-proxy-middleware to 3.0.7 or 4.1.1 (or later) once updated packages are available for the affected components.

ProductPackageStateAdvisory
Red Hat Migration Toolkit for Applications 8.1mta/mta-ui-rhel9:1785169013Fixed 2026-08-04RHSA-2026:50300
Red Hat Trusted Artifact Signer 1.3rhtas/rhtas-console-ui-rhel9:1784105894Fixed 2026-07-20RHSA-2026:42085
Cryostat 4cryostat-openshift-console-plugin-npmNot affected
Cryostat 4http-proxy-middlewareNot affected
Gatekeeper 3gatekeeper/gatekeeper-rhel9Not affected
Migration Toolkit for Applications 8mta/mta-ui-rhel8Not affected
Migration Toolkit for Containersrhmtc/openshift-migration-ui-rhel8Not affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-must-gather-rhel9Not affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-operator-bundleNot affected
Node HealthCheck Operatorworkload-availability/node-healthcheck-rhel9-operatorNot affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-console-plugin-419-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-console-plugin-pf5-rhel9Not affected
OpenShift Lightspeedopenshift-lightspeed/lightspeed-console-plugin-rhel9Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-console-plugin-pf5-rhel9Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-console-plugin-rhel8Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-console-plugin-rhel9Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel8Not affected
OpenShift Pipelinesopenshift-pipelines/pipelines-hub-ui-rhel9Not affected
OpenShift Service Mesh 2openshift-service-mesh/kiali-ossmc-rhel8Not affected
OpenShift Service Mesh 2openshift-service-mesh/kiali-rhel8Not affected
39 more in the JSON and on Red Hat's page.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-55603.

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON