Medium [CVE-2026-54273] Denial of Service via excessive pipelined requests
This medium-severity Red Hat Linux advisory covers CVE-2026-54273 affecting Exploit Intelligence, Migration Toolkit for Applications 8, OpenShift Lightspeed.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, no limit was present on the number of pipelined requests that could be queued.
An attacker may be able to use pipelined requests to use excessive amounts of memory, potentially leading to DoS. This vulnerability is fixed in 3.14.1.
An attacker could exploit this vulnerability by sending an unlimited number of pipelined requests, causing the system to consume excessive amounts of memory. This could lead to a Denial of Service (DoS), making the affected system unavailable to legitimate users.
This vulnerability is rated Moderate because an unauthenticated remote attacker can trigger denial of service against an affected aiohttp HTTP/1 server by sending a large number of pipelined requests, causing excessive memory consumption. Exploitation requires aiohttp to be deployed as an HTTP/1 server that accepts pipelined requests from untrusted clients.
Many Red Hat products ship aiohttp as a bundled dependency for client libraries, internal automation, or services that do not expose this server behavior to untrusted users. In those configurations, practical risk may be lower, but affected packages should still be updated to aiohttp 3.14.1 or later when fixes are released.
Red Hat severity: Moderate — CVSS 5.9 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-770.
Is CVE-2026-54273 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-54273 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-54273?
Upgrade to a fixed release named by Red Hat:
- 3.14.1
Confirm against the vendor advisory before you patch.
- < 3.14.1
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Mitigation checklist
- Update the aiohttp package to version 3.14.1 or later. Until updated builds are available for a given product, reduce exposure by not exposing aiohttp-based HTTP/1 servers directly to untrusted networks. A reverse proxy in front of the service can help limit abusive pipelined request patterns. Installations that use aiohttp only as an HTTP client, or that do not accept HTTP/1 pipelined requests on an aiohttp server, are not affected by this flaw.
Official advisory · high-confidence parse· fetched 14 days ago·verify at source
Get an email when Red Hat publishes the next one.
See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-48710May 26, 2026Security restriction bypass via malformed HTTP Host header
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
iPhone and Android apps · New on the App Store
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.