Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-444 (HTTP请求的解释不一致性(HTTP请求私运)) — Vulnerability Class 285

285 vulnerabilities classified as CWE-444 (HTTP请求的解释不一致性(HTTP请求私运)). AI Chinese analysis included.

CWE-444 represents a critical architectural weakness where an intermediary HTTP agent, such as a proxy or firewall, fails to interpret malformed requests consistently with the ultimate destination server. This discrepancy allows attackers to exploit the ambiguity by crafting specially designed HTTP messages that are parsed differently by the front-end and back-end systems. Consequently, an attacker can smuggle malicious requests past security controls, potentially bypassing access restrictions, injecting unauthorized commands, or performing cache poisoning attacks. To mitigate this vulnerability, developers must ensure strict alignment in HTTP parsing logic across all network components. This involves configuring proxies and servers to use identical parsing standards, validating request boundaries rigorously, and employing modern frameworks that explicitly handle ambiguous headers. Regular security testing and automated fuzzing further help identify inconsistencies before deployment, ensuring that all entities in the data flow interpret messages uniformly.

MITRE CWE Description
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.
Common Consequences (1)
Integrity, Non-Repudiation, Access Control Unexpected State, Hide Activities, Bypass Protection Mechanism
An attacker could create HTTP messages to exploit a number of weaknesses including 1) the message can trick the web server to associate a URL with another URL's webpage and caching the contents of the webpage (web cache poisoning attack), 2) the message can be structured to bypass the firewall prote…
Mitigations (4)
Implementation Use a web server that employs a strict HTTP parsing procedure, such as Apache [REF-433].
Implementation Use only SSL communication.
Implementation Terminate the client session after each request.
System Configuration Turn all pages to non-cacheable.
Examples (2)
In the following example, a malformed HTTP request is sent to a website that includes a proxy server and a web server with the intent of poisoning the cache to associate one webpage with another malicious webpage.
POST http://www.website.com/foobar.html HTTP/1.1 Host: www.website.com Connection: Keep-Alive Content-Type: application/x-www-form-urlencoded Content-Length: 0 Content-Length: 54 GET /poison.html HTTP/1.1 Host: www.website.com Bla: GET http://www.website.com/page_to_poison.html HTTP/1.1 Host: www.website.com Connection: Keep-Alive
Attack
GET /poison.html HTTP/1.1 Host: www.website.com Bla:
Result
In the following example, a malformed HTTP request is sent to a website that includes a web server with a firewall with the intent of bypassing the web server firewall to smuggle malicious code into the system.
POST /page.asp HTTP/1.1 Host: www.website.com Connection: Keep-Alive Content-Length: 49223 zzz...zzz ["z" x 49152] POST /page.asp HTTP/1.0 Connection: Keep-Alive Content-Length: 30 POST /page.asp HTTP/1.0 Bla: POST /page.asp?cmd.exe HTTP/1.0 Connection: Keep-Alive
Attack
CVE ID Title CVSS Severity Published
CVE-2026-63379 Libevent: HTTP Header smuggling — libevent 6.3 Medium 2026-08-20
CVE-2026-63382 libevent evhttp: Multiple HTTP Parser Bugs Enable Request Smuggling — libevent 9.2 Critical 2026-08-20
CVE-2026-73256 Mongoose: HTTP/1.0 detection off-by-one enables request smuggling via chunked TE — mongoose 9.1 Critical 2026-08-20
CVE-2026-73257 Mongoose: Content-Length + Transfer-Encoding coexistence enables request smuggling — mongoose 9.1 Critical 2026-08-20
CVE-2026-73051 actix-http before 3.12.1 HTTP Request Smuggling via CL.TE — actix-web 6.3 Medium 2026-08-14
CVE-2026-73495 blaze: Chunked-body trailer fields promoted into Request.headers in blaze-server (front-end header-sanitization bypass) — blaze 7.4 High 2026-08-12
CVE-2026-62899 .NET Security Feature Bypass Vulnerability — .NET 10.0 5.9 Medium 2026-08-11
CVE-2026-14180 Undertow-core: undertow:http request smuggling via oversized chunk-size bit overlap — Red Hat JBoss Enterprise Application Platform 8.1.8.GA 5.3 Medium 2026-08-11
CVE-2026-72587 Instatic - Cache Poisoning via Unauthenticated Server Island Endpoint — Instatic 6.1 Medium 2026-08-10
CVE-2026-71554 h2: Duplicate Host header could facilitate request smuggling — h2 5.3 Medium 2026-08-06
CVE-2026-71324 Traefik: Cross-user response poisoning via proxied CONNECT on Traefik's shared backend keep-alive pool — traefik 7.0 High 2026-08-06
CVE-2026-9190 HTTP request smuggling in Progress MarkLogic Server — MarkLogic Server 9.1 Critical 2026-08-05
CVE-2026-58044 nodejs node 输入验证错误漏洞 — node - - 2026-08-04
CVE-2026-69243 AIOHTTP: HTTP request smuggling via WebSocket upgrade — aiohttp 6.3 Medium 2026-08-03
CVE-2026-58047 WebPros cPanel 输入验证错误漏洞 — cPanel 5.6 Medium 2026-07-31
CVE-2026-16728 undici vulnerable to downstream response desynchronization via retry interceptor — undici 4.8 Medium 2026-07-29
CVE-2026-59898 Netty: WebSockets V07/V08 handshaker missing Connection/Upgrade validation — netty 6.3 Medium 2026-07-29
CVE-2026-59900 Netty codec-http2: Lack of Host Header Deduplication in HTTP/2→HTTP/1.x Translation Leads to Request Routing Bypass — netty 6.9 Medium 2026-07-29
CVE-2026-58155 Apache Traffic Server: Header-name length truncation enables header aliasing and request smuggling — Apache Traffic Server 9.3 Critical 2026-07-29
CVE-2026-58153 Apache Traffic Server: HTTP/2 to HTTP/1 conversion forwards origin trailers to clients unsafely — Apache Traffic Server 8.3 High 2026-07-29
CVE-2026-58150 Apache Traffic Server: HTTP/2 requests with Transfer-Encoding are not rejected, allowing request smuggling — Apache Traffic Server 10.0 Critical 2026-07-29
CVE-2026-57834 Apache Traffic Server: Malformed chunked message body allows request smuggling — Apache Traffic Server 10.0 Critical 2026-07-29
CVE-2026-24033 Apache Traffic Server: Request smuggling via chunked extension quoted-string parsing — Apache Traffic Server 7.2 High 2026-07-29
CVE-2026-15064 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by multiple vulnerabilities — WebSphere Application Server 8.7 High 2026-07-28
CVE-2026-15325 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by multiple vulnerabilities — WebSphere Application Server 8.7 High 2026-07-28
CVE-2026-15328 IBM WebSphere Application Server and WebSphere Application Server Liberty is inconsistent Interpretation of HTTP Requests — WebSphere Application Server 7.4 High 2026-07-28
CVE-2026-67182 Rouille 0.3.3 - 3.6.2 HTTP Request Smuggling via proxy Header Injection — rouille 7.5 High 2026-07-28
CVE-2026-67181 Rouille 0.3.3 - 3.6.2 HTTP Request Smuggling via proxy Transfer-Encoding Header — rouille 5.4 Medium 2026-07-28
CVE-2026-66752 tiny-http 0.12.0 HTTP Request Smuggling via Transfer-Encoding Handling — tiny-http 5.4 Medium 2026-07-28
CVE-2026-66338 Libsoup: libsoup: http request smuggling via permissive chunk-size parsing in soup_body_input_stream_read_chunked() — Red Hat Enterprise Linux 10 5.4 Medium 2026-07-24

Vulnerabilities classified as CWE-444 (HTTP请求的解释不一致性(HTTP请求私运)) represent 285 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.