Skip to main content
VulnerabilityPublished

CVE-2026-128128: AIOHTTP · WebSocket max_msg_size bypass via integer overflow

Affects homeassistant-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128128· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 17 Nov 2026, 19:19 UTC

CVSS 3.1 base score
7.5High
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 3.17.5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 upgrading to the patched version of AIOHTTP. If upgrading is not possible, users can disable the C extension by setting the environment variable AIOHTTP_NO_EXTENSIONS=1 to use the unaffected Python reader as a workaround.

Description

AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check within the C extension. This flaw allows an attacker to bypass the maximum message size restriction by sending a specially crafted WebSocket message with a declared frame length near 2^63, causing unbounded memory consumption. The issue affects versions of the homeassistant-cli starting from 0.5.0. A patch is available to address this vulnerability.

References

Community reviews

Loading reviews…