CVE•Published 2026-06-02•Modified 2026-06-05•0 articles on news•5 live references•NVD data
CVE-2026-34993Aiohttp · Aiohttp
Vulnerability data via NVD (ingested)
CVSS v3.1
6.4
MEDIUM
CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:C/C:L/I:H/A:L
EPSS percentile
18
Exploit Prediction Scoring System · top 82% of all CVEs
Weaknesses (CWE)
Description
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to version 3.14.0, using ``CookieJar.load()`` with untrusted input may allow arbitrary code execution. Most applications using this function will be doing so with the user's own data, so this is unlikely to affect many applications. Version 3.14.0 patches the issue. If an application does allow attacker controlled files to be loaded, a workaround on older releases would be to sanitize the files before loading.
Timeline
Published 2026-06-02
Modified 2026-06-05
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-34993Hosts 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-34993Country / ASN / product breakdown for the vuln query.
Censys
vulnerabilities.cve_id: CVE-2026-34993Censys host search filtered to this CVE id.
grep.app
CVE-2026-34993Public source-code mentions — fast PoC discovery.
GitHub code
CVE-2026-34993GitHub code search for direct mentions.
Google dork
"CVE-2026-34993" exploit -site:nvd.nist.govWrite-ups and news, NVD excluded.
Known PoCs on GitHub (1)
We haven't classified any articles referencing CVE-2026-34993 yet. The external references above still apply.