Cross-client response disclosure via concurrent pipeline dispatch
Published Jul 29, 2024 · Updated Nov 3, 2025
HTTP response-ordering errors in Twisted 24.3.0 and earlier allow remote attackers to receive responses intended for other clients. twisted.web's HTTPChannel dispatches multiple pipelined requests concurrently instead of buffering later requests until the active response finishes. An unauthenticated client must share a pooled reverse-proxy backend connection, allowing response data from a different client to be disclosed.
Summary
What happened
HTTP response-ordering errors in Twisted 24.3.0 and earlier allow remote attackers to receive responses intended for other clients. twisted.web's HTTPChannel dispatches multiple pipelined requests concurrently instead of buffering later requests until the active response finishes. An unauthenticated client must share a pooled reverse-proxy backend connection, allowing response data from a different client to be disclosed.
The record
- CVE
- CVE-2024-41671
- Published
- Jul 29, 2024
- Updated
- Nov 3, 2025
- Vendor
- Twisted
- Product
- Twisted
- Classifications
- CWE-444, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 29, 2024CVE 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=0 <=24.3.0
- Affected versionversion=<= 24.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Upstream disordered-pipeline proof of conceptproof of concept · demonstrated
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