CVE-2026-54275
Aiohttp ≤ 3.14.1
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-54275 is a low-severity Improper Validation of Certificate with Host Mismatch (CWE-297) vulnerability in Aiohttp Aiohttp. Its CVSS base score is 2.7 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SC-23 (Session Authenticity) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-38312
Vulnerability Data
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, the server_hostname TLS SNI check can be bypassed when an existing connection is reused. If an application makes multiple requests to the same domain, but with…
more
different per-request server_hostname parameters, then the later calls may succeed by reusing the existing connection when they should have been rejected due to the TLS SNI check. This vulnerability is fixed in 3.14.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V17.2.8
Mitigating Controls (NIST 800-53 r5) AI
Protecting session authenticity structurally requires proper certificate validation to bind the presented certificate to the intended host.
Requiring confidentiality and integrity of transmitted data necessitates correct TLS certificate validation with host-name checking.
Security engineering principles require correct implementation of certificate validation (including hostname matching) when cryptography is used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Protecting data-in-transit integrity depends on proper certificate validation to prevent MITM.
Secure development practices include coding correct certificate validation logic.
Server/service authentication via certificates directly requires correct host validation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect missing certificate validation and host-mismatch checks.
Network security controls include certificate validation and host-name verification to prevent man-in-the-middle attacks.
Security of network services requires proper TLS configuration and certificate validation for service endpoints.
Use of cryptography mandates correct implementation of certificate validation and hostname verification.
Application security requirements include secure communication and certificate validation for external services.
Secure system architecture principles require proper certificate validation to protect communications.