high · 8.2 Patched

aiohttp server lacks an initial request/header timeout

CVE-2026-111064 · GHSA-5wr8-gcqf-gqf3 · published 19 Oct 2026

How serious is it

Severity: high, CVSS score 8.2 out of 10.
No exploit prediction (EPSS) score yet.
Not on the CISA list of exploited vulnerabilities.
No public exploit in Exploit-DB.

Is your app affected by CVE-2026-111064?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

aiohttp (PyPI) <= 3.14.3

How to check

Run pip show aiohttp in your project to see the installed version, including copies pulled in by other packages.
Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.
Or run npx shippable-dev scan localhost:3000 in your project folder. It reads your lockfile and flags this vulnerability along with every other known one.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.

Upgrade aiohttp to 3.14.4 or later, commit the lockfile and redeploy.
If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

### Summary The keepalive timeout was not used during the initial portion of a request. ### Impact An attacker could keep an idle connection open indefinitely before sending any data. ### Workaround Use a reverse proxy (as recommended for all production deployments) with sensible keepalive limits.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 23 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities