Skip to main content
VulnerabilityPublished

CVE-2026-128129: AIOHTTP · Unbounded buffering of data received during an upgrade request

Affects homeassistant-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128129· High 8.2

Not known to be exploited · CVSS 8.2 High.

Data as of 17 Nov 2026, 19:19 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Homebrewhomeassistant-clipkg:brew/homeassistant-cliOther threatsAffected
  • >=0.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available and should be applied by updating AIOHTTP to the patched version as per the commit at https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df. Users should upgrade to the fixed version to prevent unbounded memory use during upgrade requests.

Description

AIOHTTP versions 0.5.0 and later have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit until the upgrade handler completes. This unbounded buffering can lead to excessive memory consumption if an attacker streams large amounts of data behind the upgrade request. The issue has been patched in the referenced commit.

References

Community reviews

Loading reviews…