Skip to main content
VulnerabilityPublished Updated

CVE-2026-111066: Aiohttp · From 2.0.0 until 3.14.4, multipart request processing can retain an unbounded number of

Affects aiohttpSource GCVE Database

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

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

Data as of 17 Nov 2026, 10:50 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.14.4
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 aiohttp to 3.14.4.

Affected software

ProductAffectedFixed in
PyPIaiohttppkg:pypi/aiohttpOther threatsAffected
  • 2.0.0 – 3.14.3
  • >=2.0.0 <3.14.4
200 affected builds
Fixed in
  • 3.14.4

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

AI-suggested

Upgrade aiohttp to version 3.14.4 or later, where this vulnerability is fixed. The vendor has released an official patch and advisory. No other mitigations are indicated.

Description

A vulnerability in aiohttp versions from 2.0.0 up to but not including 3.14.4 allows multipart request processing to retain an unbounded number of open file descriptors. This can enable an unauthenticated attacker to exhaust file descriptors by sending specially crafted multipart requests to handlers using Request.post(). The issue is fixed in version 3.14.4.

References

Community reviews

Loading reviews…