Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
CVE-2026-1002
Summary
The Vert.x Web static handler component cache can be manipulated to deny the access to static files served by the handler using specifically crafted request URI. The issue comes from an improper implementation of the C. rule of section 5.2.4 of RFC3986 and is fixed in Vert.x Core component (used by Vert.x Web): "https://github.com/eclipse-vertx/vert.x/pull/5895" Steps to reproduce Given a file served by the static handler, craft an URI that introduces a string like "bar%2F..%2F" after the last "/" char to deny the access to the URI with an HTTP 404 response. For example "https://example.com/foo/index.html" can be denied with "https://example.com/foo/bar%2F..%2Findex.html" Mitgation:Disabling Static Handler cache fixes the issue. "StaticHandler staticHandler = StaticHandler.create().setCachingEnabled(false);". Versions prior to 4.5.24 and 5.x versions prior to 5.0.7 are affected.
- LOW
- NETWORK
- NONE
- UNCHANGED
- NONE
- NONE
- NONE
- LOW
CWE-444 - HTTP Request Smuggling
Entities such as web servers, web caching proxies, and application firewalls could parse HTTP requests differently. When there are two or more such entities in the path of an HTTP request, an attacker can send a specially crafted HTTP request that is seen as two different sets of requests by the attacked devices, allowing the attacker to smuggle a request into one device without the other device being aware of it. Such a vulnerability can prove devastating, for it enables further attacks on the application, like web cache poisoning, session hijacking, cross-site scripting, security bypassing, and sensitive information exposure.
Advisory Timeline
- Published
