Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-cq5v-8q36-5273

AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response)

CVSS 7.1 HighEPSS 0.0053 · 45th percentile

Published by the GitHub Advisory Database at 3 Aug 2026, 20:51 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aiohttpPyPI<3.14.33.14.3
Identifiers
GHSA-cq5v-8q36-5273 · CVE-2026-69244 · PYSEC-2026-3545
Weakness (CWE)
CWE-125 · CWE-400 · CWE-416
Tags
Published
3 Aug 2026
Updated
10 Sept 2026

Machine-written summary

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

The aiohttp package, versions before 3.14.3, is vulnerable to an out-of-bounds heap read in its C HTTP response parser while it builds an error message for a malformed response. An attacker-controlled server, or possibly an accidental malformed response, could cause a denial of service in the client. Upgrade to aiohttp 3.14.3 or later. If you cannot upgrade, set the environment variable AIOHTTP_NO_EXTENSIONS=1 to use the Python parser, which the source says is unaffected.

Written 1 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
7.1 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0053, the 45th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 25 Jul 2026, 12:18 UTC Published by the maintainers as a GitHub repository advisory
  2. 31 Oct 2026, 14:10 UTC First seen by agentprime
  3. 31 Oct 2026, 14:10 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.