Skip to main content
No exploitation reportedFix available

CVE-2026-123817

AIOHTTP WebSocket frame reassembly permits excessive memory consumption from tiny reads

No exploitation reported by the sources we read.

  • Published2026-11-09
  • Fixed in3.14.4
  • WeaknessCWE-770

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.

Timeline

dates in UTC
  1. 2026-11-0921:17CVE publishedCNA

Versions per branch

NVD · OSV
Aiohttp
BranchAffectedFixed in
3.14< 3.14.43.14.4

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As GitHub_M, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • aio-libs aiohttp
    Affected
    • = < 3.14.4no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-09

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • aiohttpRoot:PyPIall versions · fixed in 3.13.3+aikido.18
  • aiohttpRoot:PyPIall versions · fixed in 3.8.6+aikido.17
  • aiohttpRoot:PyPIall versions · fixed in 3.14.3+aikido.2
  • aiohttpRoot:PyPIall versions · fixed in 3.13.3+aikido.19
  • airflow-2Chainguardall versions · no fixed version listed
  • airflow-core-2Chainguardall versions · fixed in 2.11.2-r14
  • awxChainguardall versions · fixed in 24.6.1-r71
  • commercial-gitlab-toolbox-ee-19.1Chainguardall versions · fixed in 19.1.9-r0and 1 other package

36 more package ranges on OSV.dev

Full record on NVD

Fix

  1. Update Aiohttp to 3.14.4

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/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:X
Published
2026-11-09
Last Modified
2026-11-18
NVD status
Analyzed
GitHub Advisory
GHSA-2g87-pp6c-29x5

Frequently asked questions

What is CVE-2026-123817?

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.

Is CVE-2026-123817 actively exploited?

Active exploitation of CVE-2026-123817 has not been confirmed. Its EPSS score was 0.3% on 2026-11-17, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-123817?

CVE-2026-123817 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running aiohttp? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record