Service interruption via unbounded pipelined request queue
Published Jun 22, 2026 · Updated Jun 22, 2026
Resource exhaustion in aiohttp before 3.14.1 allows remote attackers to interrupt server availability with pipelined HTTP/1 requests. RequestHandler placed parsed-but-unhandled requests in its _messages deque without a count limit while a handler remained busy. An unauthenticated client can keep one handler occupied and pipeline more requests on the same connection until memory pressure interrupts the service.
Summary
What happened
Resource exhaustion in aiohttp before 3.14.1 allows remote attackers to interrupt server availability with pipelined HTTP/1 requests. RequestHandler placed parsed-but-unhandled requests in its _messages deque without a count limit while a handler remained busy. An unauthenticated client can keep one handler occupied and pipeline more requests on the same connection until memory pressure interrupts the service.
The record
- CVE
- CVE-2026-54273
- Published
- Jun 22, 2026
- Updated
- Jun 22, 2026
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-770, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 22, 2026CVE publishedPublication date reported by the CVE source.
- Jun 22, 2026Record 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.14.1
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
No public exploit references are available in this record.
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