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-115823 Starman versions before 0.4019 for Perl send response bodies for HEAD requests, desynchronizing responses on keep-alive connections - - 2026-10-25
CVE-2026-115877 Twisted: HTTP Request Smuggling in twisted.web via a Bare CR or LF in a Header Value — twisted 5.4 Medium 2026-10-23
CVE-2026-112212 Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in GitLab — GitLab 7.5 High 2026-10-21
CVE-2026-111809 Apache Traffic Server: HEAD requests carrying Content-Length or Transfer-Encoding enable request smuggling — Apache Traffic Server 9.3 Critical 2026-10-21
CVE-2026-111816 Apache Traffic Server: A malformed 302 response bypasses parse-error rejection through the Transfer-Encoding: chunked carve-out — Apache Traffic Server 9.3 Critical 2026-10-21
CVE-2025-55702 Apache Traffic Server: An unread Expect: 100-continue request body is framed as a new request — Apache Traffic Server 8.7 High 2026-10-21
CVE-2025-31699 Apache Traffic Server: Origin connection still owed a request body is reused, enabling request smuggling — Apache Traffic Server 8.9 High 2026-10-21
CVE-2026-86146 Apache bRPC: HTTP Request Smuggling and Header Injection via Lenient HTTP/1.1 Header Parsing — Apache bRPC - - 2026-10-21
CVE-2026-93003 NetX Duo Web HTTP server interprets request body content as HTTP header fields — Eclipse ThreadX - NetX Duo 6.9 Medium 2026-10-20
CVE-2026-111750 AIOHTTP: Pure-Python parser request smuggling — aiohttp 6.3 Medium 2026-10-19
CVE-2026-88829 Busybox: busybox: http request smuggling via pipelined requests in httpd reverse proxy — Red Hat Hardened Images 7.2 High 2026-10-14
CVE-2026-88092 ASP.NET Core Tampering Vulnerability — ASP.NET Core 10.0 9.4 Critical 2026-10-13
CVE-2026-70188 ASP.NET Core Security Feature Bypass Vulnerability — ASP.NET Core 10.0 9.1 Critical 2026-10-13
CVE-2026-61642 Squid Request Smuggling in HTTP Transfer-Encoding — squid 7.7 High 2026-10-13
CVE-2026-77803 Front-end Desynchronization Vulnerability in Progress® Telerik® Fiddler® Classic — Progress® Telerik® Fiddler® Classic 3.6 Low 2026-10-05
CVE-2026-77802 HTTP Request Smuggling Vulnerability in Progress® Telerik® Fiddler® Classic — Progress® Telerik® Fiddler® Classic 6.3 Medium 2026-10-05
CVE-2026-63718 Apache HTTP Server: mod_proxy_uwsgi Transfer-Encoding response smuggling — Apache HTTP Server - - 2026-10-01
CVE-2026-103399 Libsoup: soupserver: http/1 request smuggling via undrained expect: 100-continue body — Red Hat Enterprise Linux 10 5.3 Medium 2026-09-30
CVE-2026-94194 Mint HTTP/1 client applies chunked framing when chunked is not the final transfer coding, enabling response smuggling through intermediaries — mint 6.3 Medium 2026-09-28
CVE-2026-88773 HTTP Request Smuggling — ADC 9.3 Critical 2026-09-27
CVE-2026-100724 http4k before 6.49.0.0 Host Header Routing Bypass via reverseProxy — http4k 5.4 Medium 2026-09-27
CVE-2026-100666 Netty 4.2.0 through 4.2.16 Response Desynchronization via HttpServerCodec — netty 7.3 High 2026-09-26
CVE-2026-100659 Netty 4.2.0 through 4.2.17 HTTP/3 Request Routing Bypass — netty 6.5 Medium 2026-09-26
CVE-2026-86350 Apache Tomcat: Regression in fix for CVE-2026-41293 can trigger request header mix-up — Apache Tomcat - - 2026-09-23
CVE-2026-77756 Apache Tomcat: Transfer-Encoding honored for HTTP/1.0 requests — Apache Tomcat - - 2026-09-23
CVE-2026-73548 Envoy: Cross-user response poisoning via a generic (non-WebSocket) HTTP upgrade on Envoy's shared backend pool — envoy 7.5 High 2026-09-21
CVE-2026-82672 Unvalidated chunk-size line tail in Mint HTTP/1 client enables response smuggling against strict intermediaries on pooled connections — mint 6.3 Medium 2026-09-19
CVE-2026-93574 Io.netty/netty-codec-http: netty: http request smuggling via post-digit whitespace in chunk-size parsing — Red Hat Build of Debezium 3.6 6.5 Medium 2026-09-18
CVE-2026-11722 IBM WebSphere Application Server and IBM WebSphere Application Server - Liberty HTTP Request Smuggling — WebSphere Application Server 4.8 Medium 2026-09-18
CVE-2026-11710 IBM WebSphere Application Server is affected by an HTTP request smuggling vulnerability — WebSphere Application Server 6.5 Medium 2026-09-18

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