Proxy rule bypass via conflicting message framing
Published Nov 14, 2023 · Updated Nov 3, 2025
HTTP request smuggling in aiohttp before 3.8.0 allows remote attackers to bypass proxy rules through conflicting message framing. The HTTP parser treats any Transfer-Encoding value containing chunked as chunked, while affected releases fail to reject a simultaneous Content-Length header. Exploitation requires a reverse proxy that honors Content-Length while aiohttp honors Transfer-Encoding, enabling persistent-socket poisoning and cross-user header exposure.
Summary
What happened
HTTP request smuggling in aiohttp before 3.8.0 allows remote attackers to bypass proxy rules through conflicting message framing. The HTTP parser treats any Transfer-Encoding value containing chunked as chunked, while affected releases fail to reject a simultaneous Content-Length header. Exploitation requires a reverse proxy that honors Content-Length while aiohttp honors Transfer-Encoding, enabling persistent-socket poisoning and cross-user header exposure.
The record
- CVE
- CVE-2023-47641
- Published
- Nov 14, 2023
- Updated
- Nov 3, 2025
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 14, 2023CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.8.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA conflicting-framing proof of conceptproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo