CWE · MITRE source
CWE-444Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
HTTP requests or responses ("messages") can be malformed or unexpected in ways that cause web servers or clients to interpret the messages in different ways than intermediary HTTP agents such as load balancers, reverse proxies, web caching proxies, application firewalls, etc. For example, an adversary may be able to add duplicate or different header fields that a client or server might interpret as one set of messages, whereas the intermediary might interpret the same sequence of bytes as a different set of messages. For example, discrepancies can arise in how to handle duplicate headers like two Transfer-encoding (TE) or two Content-length (CL), or the malicious HTTP message will have different headers for TE and CL. The inconsistent parsing and interpretation of messages can allow the adversary to "smuggle" a message to the client/server without the intermediary being aware of it. This weakness is usually the result of the usage of outdated or incompatible HTTP protocol versions in the HTTP agents.
Last updated: 20 August 2026 20:22 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 1 framework(s): CAPEC 2 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (0)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2022-22536 KEV UPD | 10.0 | 10.0 | 0.9795 | 2022-02-09 |
CVE-2023-25690 UPD | 9.9 | 9.8 | 0.8451 | 2023-03-07 |
CVE-2021-30180 UPD | 9.6 | 9.8 | 0.6043 | 2021-06-01 |
CVE-2019-15605 UPD | 9.5 | 9.8 | 0.5713 | 2020-02-07 |
CVE-2023-41265 KEV UPD | 9.4 | 9.6 | 0.8447 | 2023-08-29 |
CVE-2023-48365 KEV UPD | 9.4 | 9.6 | 0.2468 | 2023-11-15 |
CVE-2025-55315 UPD | 9.4 | 9.9 | 0.6584 | 2025-10-14 |
CVE-2022-22720 UPD | 8.8 | 9.8 | 0.2819 | 2022-03-14 |
CVE-2017-7658 UPD | 8.6 | 9.8 | 0.2099 | 2018-06-26 |
CVE-2025-61884 KEV UPD | 8.5 | 7.5 | 0.9779 | 2025-10-12 |
CVE-2017-7657 UPD | 8.4 | 9.8 | 0.1615 | 2018-06-26 |
CVE-2020-9490 UPD | 8.4 | 7.5 | 0.8974 | 2020-08-07 |
CVE-2015-5739 UPD | 8.2 | 9.8 | 0.0963 | 2017-10-18 |
CVE-2020-11993 UPD | 8.1 | 7.5 | 0.5872 | 2020-08-07 |
CVE-2022-29361 UPD | 8.1 | 9.8 | 0.0807 | 2022-05-25 |
CVE-2024-41110 UPD | 8.1 | 9.9 | 0.1650 | 2024-07-24 |
CVE-2019-20445 UPD | 7.9 | 9.1 | 0.1347 | 2020-01-29 |
CVE-2020-10108 UPD | 7.9 | 9.8 | 0.0397 | 2020-03-12 |
CVE-2021-45468 UPD | 7.9 | 9.8 | 0.0399 | 2022-01-14 |
CVE-2015-5740 UPD | 7.8 | 9.8 | 0.0366 | 2017-10-18 |
CVE-2016-10711 UPD | 7.8 | 9.8 | 0.0284 | 2018-01-29 |
CVE-2020-10109 UPD | 7.8 | 9.8 | 0.0329 | 2020-03-12 |
CVE-2019-17559 UPD | 7.8 | 9.8 | 0.0317 | 2020-03-23 |
CVE-2019-17565 UPD | 7.8 | 9.8 | 0.0317 | 2020-03-23 |
CVE-2020-1944 UPD | 7.8 | 9.8 | 0.0273 | 2020-03-23 |