Medium [CVE-2026-54274] Denial of Service via incomplete websocket frame payloads
This medium-severity Red Hat Linux advisory covers CVE-2026-54274 affecting Exploit Intelligence, Migration Toolkit for Applications 8, OpenShift Lightspeed.
Android app · Google Play
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 32 official vendor sources and 160+ reviewed platform categories.
Summary
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, if an attacker sends large incomplete websocket frame payloads, it may be possible to bypass the usual size limits on memory use.
This vulnerability is fixed in 3.14.1. This can bypass normal memory usage limits, potentially leading to a Denial of Service (DoS) where the affected system becomes unavailable.
Exploitation requires aiohttp deployed as a network-facing HTTP server that exposes WebSocket endpoints to untrusted clients. Many Red Hat products ship aiohttp as a bundled dependency for client libraries, internal automation, or services that do not expose WebSocket listeners 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. Affected Red Hat products: Exploit Intelligence; Migration Toolkit for Applications 8; OpenShift Lightspeed; Red Hat AI Inference Server; Red Hat Ansible Automation Platform 2; Red Hat Ansible Automation Platform Ansible Core 2; Red Hat Discovery 2; Red Hat Enterprise Linux AI (RHEL AI) 3; Red Hat OpenShift AI (RHOAI); Red Hat Satellite 6.
- < 3.14.1
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
Mitigation checklist
- Update the aiohttp package to version 3.14.1 or later. Until updated builds are available, reduce exposure by not exposing aiohttp-based HTTP servers with WebSocket endpoints directly to untrusted networks. A reverse proxy or load balancer in front of the service can help limit abusive WebSocket traffic. Installations that use aiohttp only as an HTTP client, or that do not expose WebSocket endpoints, are not affected by this flaw.
Official advisory · high-confidence parse· fetched 15 days ago·verify at source
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.