Skip to main content
VulnerabilityPublished Updated

CVE-2026-111750: AIOHTTP · Pure-Python parser request smuggling

Affects scrapySource GCVE Database

0
Compare
Authoritative record:CVE-2026-111750· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 2.19.0_2 when convenient.

Data as of 17 Nov 2026, 17:49 UTC

CVSS 4.0 base score
6.3Medium
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.06.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:L/SC:N/SI:L/SA:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Oct 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 fix is available in AIOHTTP version 2.19.0_2. Users should upgrade to this version to remediate the vulnerability. Alternatively, switching to the default C parser mitigates the risk if upgrading is not immediately possible.

Description

The pure Python HTTP parser in AIOHTTP is vulnerable to an HTTP request smuggling attack when used instead of the default C parser. This affects applications using the Python parser, such as those with the AIOHTTP_NO_EXTENSIONS environment or non-standard wheel installations. The vulnerability is fixed in version 2.19.0_2. Users are advised to switch to the default C parser to mitigate the risk.

References

Community reviews

Loading reviews…