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: 09 May 2026 03:25 UTC
NIST 800-53 r5 controls that address this weakness (0)AI
| 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 | 9.6 | 10.0 | 0.9383 | 2022-02-09 |
CVE-2023-41265 KEV | 9.5 | 9.6 | 0.9241 | 2023-08-29 |
CVE-2023-48365 KEV | 7.4 | 9.6 | 0.5866 | 2023-11-15 |
CVE-2022-32213 | 6.6 | 6.5 | 0.8846 | 2022-07-14 |
CVE-2022-32215 | 6.5 | 6.5 | 0.8739 | 2022-07-14 |
CVE-2025-61884 KEV | 6.4 | 7.5 | 0.4832 | 2025-10-12 |
CVE-2020-9490 | 6.1 | 7.5 | 0.7628 | 2020-08-07 |
CVE-2023-25690 | 6.1 | 9.8 | 0.6818 | 2023-03-07 |
CVE-2019-20372 | 5.3 | 5.3 | 0.7083 | 2020-01-09 |
CVE-2023-46589 | 5.0 | 7.5 | 0.5789 | 2023-11-28 |
CVE-2023-33193 | 4.8 | 9.1 | 0.4940 | 2023-05-30 |
CVE-2021-45468 | 4.0 | 9.8 | 0.3328 | 2022-01-14 |
CVE-2019-15605 | 3.9 | 9.8 | 0.3225 | 2020-02-07 |
CVE-2022-29361 | 3.8 | 9.8 | 0.3111 | 2022-05-25 |
CVE-2022-26377 | 3.8 | 7.5 | 0.3867 | 2022-06-09 |
CVE-2022-32214 | 3.7 | 6.5 | 0.3929 | 2022-07-14 |
CVE-2022-22720 | 3.6 | 9.8 | 0.2746 | 2022-03-14 |
CVE-2020-11993 | 3.5 | 7.5 | 0.3336 | 2020-08-07 |
CVE-2005-2088 | 3.3 | 0.0 | 0.5429 | 2005-07-05 |
CVE-2023-25725 | 3.0 | 9.1 | 0.2004 | 2023-02-14 |
CVE-2020-15049 | 2.9 | 9.9 | 0.1565 | 2020-06-30 |
CVE-2015-5739 | 2.7 | 9.8 | 0.1188 | 2017-10-18 |
CVE-2019-20444 | 2.7 | 9.1 | 0.1403 | 2020-01-29 |
CVE-2022-2466 | 2.7 | 9.8 | 0.1278 | 2022-08-31 |
CVE-2017-7658 | 2.5 | 9.8 | 0.0861 | 2018-06-26 |