AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Host-Only scope on an existing parent-domain cookie can be removed by a subdomain. A user who accesses an untrusted subdomain can consequently have host-only protections stripped from cookies, although impact is limited when applications do not reflect those cookies to a browser. This issue is fixed in version 3.14.4.
CVE-2026-111749
LOWPre-NVD 2.32.3
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-104485 (ENISA EUVD) · GHSA-gx76-c99x-2c96 (GitHub Security Advisories)Source: ENISA EUVD
2.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 2.3Exploit: None knownExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 2.3
- EG Score
- 2.3LOWmedium confidence
- EG Risk
- 26EG Risk 26/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity23% × 45%Impact severity (EG Severity): CVSS 2.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 32nd
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (2.3): severity, escalated by confirmed exploitation. This CVE's 2.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 2.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 60 days if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 19, 2026
Last Modified
October 22, 2026
References (3)
- security-advisories@githubhttps://github.com/aio-libs/aiohttp/commit/6a07c171ef9f3be583e2907dcd1931372efca8d6
- security-advisories@githubhttps://github.com/aio-libs/aiohttp/releases/tag/v3.14.4
- security-advisories@githubhttps://github.com/aio-libs/aiohttp/security/advisories/GHSA-gx76-c99x-2c96
Vendor Advisories for CVE-2026-111749(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| aiohttp | 0.1 ... 3.9.5 (310 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 9× in last 7d / 18× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-29 18:19 UTCEG score recompute
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 14:52 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-22 21:31 UTCEG score recompute
- 2026-10-22 21:01 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 20th percentile
- 2026-10-19 21:13 UTCEG score recompute
- 2026-10-19 17:20 UTCEG score recomputeFirst assessed: 2.3 LOW
- 2026-10-19 17:17 UTCMITRE cvelistV5first tracked
Related CVEs(same product + same CWE)
Same product
10 shownPyPI:aiohttp
Frequently asked(5)
What is CVE-2026-111749?
CVE-2026-111749 is a low-severity vulnerability; its CVE record was published on October 19, 2026. AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Host-Only scope on an existing parent-domain cookie can be removed by a subdomain. A user who accesses an untrusted subdomain can consequently have host-only protections stripped from cookies, although…
When was the CVE record for CVE-2026-111749 published?
The CVE record for CVE-2026-111749 was published on October 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 22, 2026; the record at its source may have been updated since.
Is CVE-2026-111749 actively exploited?
CVE-2026-111749 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-111749?
CVE-2026-111749 has a CVSS base score of 2.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-111749?
A fix for CVE-2026-111749 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-111749 are linked in the Vendor Advisories panel on this page.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-111749
Is Your Infrastructure Affected by CVE-2026-111749?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.