Skip to main content
VulnerabilityPublished Updated

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

Affects checkovSource GCVE Database

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

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

Data as of 17 Nov 2026, 18:38 UTC

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

Affected software

ProductAffectedFixed in
Homebrewcheckovpkg:brew/checkovOther threatsAffected
  • >=2.0.615 <3.3.30
Fixed in
  • 3.3.30

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 Checkov version 3.3.30 that fixes this vulnerability. Users should upgrade to version 3.3.30 or later to remediate the issue. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-111066 is a high-severity vulnerability in the AIOHTTP library used by the Checkov product. It allows an attacker to exhaust file descriptors by sending specially crafted multipart requests to handlers using Request.post(), potentially causing resource exhaustion and denial of service. The issue affects Checkov versions from 2.0.615 up to but not including 3.3.30. A fix is available in version 3.3.30.

References

Community reviews

Loading reviews…