Skip to main content
VulnerabilityPublished Updated

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

Affects modalSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:18 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 1.6.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 17 Nov 2026.

What to do

Upgrade modal to 1.6.2.

Affected software

ProductAffectedFixed in
Homebrewmodalpkg:brew/modalOther threatsAffected
  • >=1.5.3 <1.6.2
Fixed in
  • 1.6.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 Modal version 1.6.2 that fixes this issue. Users should upgrade to this version. Additionally, deploying a reverse proxy with sensible keepalive limits is recommended as a workaround and best practice for production environments.

Description

The aiohttp server component in Modal versions 1.5.3 up to but not including 1.6.2 lacks an initial request or header timeout. This allows an attacker to keep an idle connection open indefinitely before sending any data, potentially leading to resource exhaustion. A fix is available in version 1.6.2. The recommended mitigation is to use a reverse proxy with sensible keepalive limits, as advised for all production deployments.

References

Community reviews

Loading reviews…