Skip to main content
VulnerabilityPublished

CVE-2026-128130: AIOHTTP · Pure-Python parser request replay and buffer growth behind a declined upgrade

Affects scrapySource GCVE Database

0
Compare
Authoritative record:CVE-2026-128130· High 8.3

Not known to be exploited · CVSS 8.3 High : upgrade to 2.19.0_2 soon.

Data as of 17 Nov 2026, 17:48 UTC

CVSS 4.0 base score
8.3High
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.3
Patch
Available – fixed in 2.19.0_2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/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

Upgrade scrapy to 2.19.0_2.

Affected software

ProductAffectedFixed in
Homebrewscrapypkg:brew/scrapyOther threatsAffected
  • >=2.19.0 <2.19.0_2
Fixed in
  • 2.19.0_2

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

AI-suggested

A patch is available in version 2.19.0_2 that fixes this vulnerability. Users should upgrade to this fixed version. Alternatively, switching to the default C parser avoids the issue. No other mitigations are specified.

Description

A vulnerability in the pure-Python HTTP parser used by AIOHTTP can cause excessive memory consumption and repeated processing of pipelined requests when the request queue is full and an upgrade request is declined. This affects users relying on the Python parser instead of the default C parser. The issue is fixed in version 2.19.0_2.

References

Community reviews

Loading reviews…