CVE-2026-67182: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in tomaka rouille
Rouille 0.3.3 through 3.6.2 contains an HTTP request smuggling vulnerability that allows remote attackers to bypass access controls by injecting bare line feed characters (0x0A) into client-supplied request header values that are copied verbatim to upstream connections without validation. Attackers can craft a header value containing a complete additional HTTP request that is interpreted as a separate request by backends such as Go net/http and Python http.server, causing the backend to process a smuggled request with attacker-chosen method, path, and headers that bypasses the rouille handler's access control logic.
AI Analysis
Technical Summary
CVE-2026-67182 describes an HTTP request smuggling vulnerability in the tomaka rouille HTTP library affecting versions 0.3.3 through 3.6.2. The issue arises because client-supplied request header values containing bare line feed characters (0x0A) are copied verbatim to upstream connections without validation. Attackers can craft headers that embed a complete additional HTTP request, which backend servers like Go net/http and Python http.server interpret as separate requests. This bypasses rouille's access control logic, allowing unauthorized requests to be processed by the backend.
Potential Impact
The vulnerability enables remote attackers to bypass access controls by injecting smuggled HTTP requests that the backend processes independently. This can lead to unauthorized access or actions being performed on the backend server, undermining the security controls implemented by rouille. The CVSS 4.0 score of 6.9 reflects a medium severity with network attack vector, low attack complexity, and partial impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, users should consider implementing additional validation or filtering of HTTP headers to prevent injection of bare line feed characters and monitor for unusual request patterns at backend servers.
CVE-2026-67182: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') in tomaka rouille
Description
Rouille 0.3.3 through 3.6.2 contains an HTTP request smuggling vulnerability that allows remote attackers to bypass access controls by injecting bare line feed characters (0x0A) into client-supplied request header values that are copied verbatim to upstream connections without validation. Attackers can craft a header value containing a complete additional HTTP request that is interpreted as a separate request by backends such as Go net/http and Python http.server, causing the backend to process a smuggled request with attacker-chosen method, path, and headers that bypasses the rouille handler's access control logic.
CVSS v4.0
Score 6.9medium
Affected software
tomaka
rouille
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-67182 describes an HTTP request smuggling vulnerability in the tomaka rouille HTTP library affecting versions 0.3.3 through 3.6.2. The issue arises because client-supplied request header values containing bare line feed characters (0x0A) are copied verbatim to upstream connections without validation. Attackers can craft headers that embed a complete additional HTTP request, which backend servers like Go net/http and Python http.server interpret as separate requests. This bypasses rouille's access control logic, allowing unauthorized requests to be processed by the backend.
Potential Impact
The vulnerability enables remote attackers to bypass access controls by injecting smuggled HTTP requests that the backend processes independently. This can lead to unauthorized access or actions being performed on the backend server, undermining the security controls implemented by rouille. The CVSS 4.0 score of 6.9 reflects a medium severity with network attack vector, low attack complexity, and partial impact on integrity and availability.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a patch is available, users should consider implementing additional validation or filtering of HTTP headers to prevent injection of bare line feed characters and monitor for unusual request patterns at backend servers.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-07-28T16:06:49.773Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a68de689c2644c7f8e9c22c
Added to database: 07/28/2026, 16:52:56 UTC
Last enriched: 07/29/2026, 23:33:16 UTC
Last updated: 09/10/2026, 20:01:15 UTC
Views: 88
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.