Skip to main content
VulnerabilityPublished Updated

CVE-2026-111066: AIOHTTP · File descriptor exhaustion in multipart requests

Affects lue-readerSource GCVE Database

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

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

Data as of 17 Nov 2026, 18:20 UTC

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

Affected software

ProductAffectedFixed in
Homebrewlue-readerpkg:brew/lue-readerOther threatsAffected
  • >=0.2.0 <0.5.0_4
Fixed in
  • 0.5.0_4

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 0.5.0_4 of lue-reader. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated.

Description

CVE-2026-111066 is a vulnerability in the lue-reader product where specially crafted multipart HTTP requests can exhaust file descriptors. This occurs if a handler uses the Request.post() method, potentially allowing an attacker to consume an unlimited number of file descriptors and cause resource exhaustion. The issue affects versions from 0.2.0 up to but not including 0.5.0_4. A fix is available in version 0.5.0_4.

References

Community reviews

Loading reviews…