Skip to main content
VulnerabilityPublished Updated

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

Affects apmSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:49 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 0.34.0
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 apm to 0.34.0.

Affected software

ProductAffectedFixed in
Homebrewapmpkg:brew/apmOther threatsAffected
  • >=0.26.0 <0.34.0
Fixed in
  • 0.34.0

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 apm version 0.34.0 that fixes this issue. Users should upgrade to version 0.34.0 or later. As a workaround, deploying a reverse proxy with sensible keepalive timeout limits is recommended and aligns with best practices for production environments.

Description

The aiohttp server component in apm versions from 0.26.0 up to but not including 0.34.0 lacks an initial request/header timeout, allowing an attacker to keep an idle connection open indefinitely before sending any data. This issue has been fixed in version 0.34.0. The vulnerability has a high severity with a CVSS score of 8.2. A recommended workaround is to use a reverse proxy with sensible keepalive limits, which is advised for all production deployments.

References

Community reviews

Loading reviews…