Advisory record · GHSA-27mf-ghqm-j3j8

aiohttp has a memory leak when middleware is enabled when requesting a resource with a non-allowed method

CVSS 8.7 HighEPSS 0.0059 · 48th percentile

Published by the GitHub Advisory Database at 18 Nov 2024, 21:02 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI>=3.10.6, <3.10.113.10.11
Identifiers
GHSA-27mf-ghqm-j3j8 · CVE-2024-52303 · PYSEC-2026-1096
Weakness (CWE)
CWE-772
Published
18 Nov 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of aiohttp from 3.10.6 before 3.10.11 leak memory when middleware is enabled and a request produces a MatchInfoError, such as a request for a resource with a method that is not allowed. Each such request adds an entry to a cache, so an attacker sending many hundreds of thousands or millions of these requests could exhaust server memory. Upgrade to aiohttp 3.10.11 or later.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0059, the 48th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 18 Nov 2024, 19:49 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:35 UTC First seen by agentprime
  3. 31 Oct 2026, 14:35 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.