Skip to main content
VulnerabilityPublished Updated

CVE-2026-111064: Scrapy · aiohttp server lacks an initial request/header timeout

Affects scrapySource GCVE Database

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

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

Data as of 17 Nov 2026, 17:50 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
Patch
Available – fixed in 2.19.0_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 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 patch is available in Scrapy version 2.19.0_2 that addresses this vulnerability. Users should upgrade to this fixed version. Additionally, deploying a reverse proxy with sensible keepalive timeout limits is recommended as a workaround and best practice for production deployments.

Description

The aiohttp server used in Scrapy versions from 2.19.0 up to but not including 2.19.0_2 lacks an initial request/header timeout, allowing an attacker to keep an idle connection open indefinitely before sending any data. This can lead to resource exhaustion. A fix is available in version 2.19.0_2. The recommended mitigation is to use a reverse proxy with sensible keepalive limits, which is advised for all production deployments.

References

Community reviews

Loading reviews…