CVE•Published 2026-06-22•Modified 2026-06-26•0 articles on news•5 live references•NVD data
CVE-2026-54275Aiohttp · Aiohttp
Vulnerability data via NVD (ingested)
CVSS v3.1
7.5
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS percentile
17
Exploit Prediction Scoring System · top 83% of all CVEs
Weaknesses (CWE)
Description
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 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.
Timeline
Published 2026-06-22
Modified 2026-06-26
External references
Search for exposed instances
Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).
Shodan · vuln tag0 hosts
vuln:CVE-2026-54275Hosts Shodan has explicitly fingerprinted as vulnerable.
Shodan · product
product:"Aiohttp Aiohttp"All exposed Aiohttp Aiohttp instances — cross-reference with the CVE's affected-version range.
Shodan · banner/body mention
http.html:"Aiohttp"HTTP body or banner mentions "Aiohttp" — catches deploys Shodan didn't identify as a product.
More intel sources (5)
Shodan report
vuln:CVE-2026-54275Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-54275Censys host search filtered to this CVE id.
grep.app
CVE-2026-54275Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-54275GitHub code search for direct mentions.
Google dork
"CVE-2026-54275" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub
No public proof-of-concept repositories found for CVE-2026-54275 on GitHub.
We haven't classified any articles referencing CVE-2026-54275 yet. The external references above still apply.