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-50197 Skipper: opaAuthorizeRequestWithBody filter bypasses OPA policy on Transfer-Encoding: chunked / HTTP/2 requests — skipper - - 2026-07-17
CVE-2026-59249 Sign-tolerant HTTP/1 chunk-size parser in Mint enables response smuggling against strict intermediaries on pooled connections — mint - - 2026-07-16
CVE-2026-12606 Eclipse Glassfish 输入验证错误漏洞 — Eclipse GlassFish 6.3 Medium 2026-07-14
CVE-2026-27690 HTTP Request Smuggling in SAP Approuter — SAP Approuter 9.1 Critical 2026-07-14
CVE-2025-3110 OpenVPN Access Server 输入验证错误漏洞 — Access Server - - 2026-07-08
CVE-2026-11541 Inconsistent Interpretation of HTTP Requests in CICS Transaction Gateway for Multiplatforms. — CICS Transaction Gateway for Multiplatforms 7.4 High 2026-06-30
CVE-2026-11806 IBM WebSphere Application Server Liberty is affected by a an arbitrary file read vulnerability — WebSphere Application Server - Liberty 7.2 High 2026-06-30
CVE-2026-13763 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in AWS Application Load Balancer with AWS WAF — AWS Application Load Balancer 9.8 Critical 2026-06-29
CVE-2026-13762 HTTP/2 Stream Parser Confusion Body-Inspection Bypass in Amazon CloudFront with AWS WAF — Amazon CloudFront 9.8 Critical 2026-06-29
CVE-2026-58055 nghttp2 nghttpx - HTTP Request/Response Smuggling via Upgrade Request with Content-Length — nghttp2 5.4 Medium 2026-06-28
CVE-2026-48743 Envoy: HTTP/3 to HTTP/1 request smuggling via headers-only request with nonzero Content-Length — envoy 7.5 High 2026-06-26
CVE-2026-48746 vLLM: OpenAI auth bypass — vllm 9.1 Critical 2026-06-22
CVE-2026-8646 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by multiple vulnerabilities — WebSphere Application Server 7.4 High 2026-06-22
CVE-2026-48979 PHP Standard Library: HTTP/2 server-side missing content-length validation enables request smuggling — php-standard-library 7.5 High 2026-06-17
CVE-2026-54388 Tinyproxy - HTTP Request Smuggling via Duplicate Content-Length Headers — tinyproxy 9.1 Critical 2026-06-17
CVE-2026-54387 Tinyproxy - HTTP Request Smuggling via CL/TE Desynchronization — tinyproxy 9.1 Critical 2026-06-17
CVE-2026-50020 Netty's HttpObjectDecoder skips arbitrary initial control characters when only initial CRLF characters are permitted — netty 5.3 Medium 2026-06-12
CVE-2026-6338 HTTP request smuggling in Kong Enteprise Gateway — Kong Enterprise Gateway - - 2026-06-11
CVE-2026-41853 Spring Framework Multipart Request Smuggling in Spring MVC and WebFlux — Spring Framework 5.3 Medium 2026-06-09
CVE-2026-44546 Header injection via WebSocket upgrade parser differential allows ASGI scope header spoofing — daphne 3.7 Low 2026-06-03
CVE-2026-50052 Varnish Cache和Vinyl Cache 环境问题漏洞 — Vinyl Cache - - 2026-06-03
CVE-2026-49753 HTTP response smuggling in Mint HTTP/1 client via lenient Content-Length parsing — mint - - 2026-06-02
CVE-2026-6324 Libsoup: libsoup: http request smuggling via unsigned to signed conversion error — Red Hat Enterprise Linux 10 4.8 Medium 2026-05-29
CVE-2026-47676 Hono: app.mount() strips mount prefix using undecoded path, causing incorrect routing for percent-encoded paths — hono 5.3 Medium 2026-05-28
CVE-2026-48710 Starlette has missing Host header validation that poisons request.url.path, bypassing path-based security checks — starlette 6.5 Medium 2026-05-26
CVE-2026-8620 IBM WebSphere Application Server and WebSphere Application Server Liberty are affected by multiple vulnerabilities when using when using Web Server Plug-ins — Web Server Plug-ins for WebSphere Application Server and WebSphere Liberty 7.5 High 2026-05-26
CVE-2026-42585 Netty: HTTP Request Smuggling due to malformed Transfer-Encoding — netty 6.5 Medium 2026-05-13
CVE-2026-42584 Netty: HttpClientCodec response desynchronization — netty 7.3 High 2026-05-13
CVE-2026-42580 Netty: HTTP Request Smuggling due to incorrect chunk size parsing — netty 6.5 Medium 2026-05-13
CVE-2026-42581 Netty: HTTP/1.0 TE+CL Coexistence Bypasses Smuggling Sanitization — netty 5.8 Medium 2026-05-13

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