Answer in brief
CVE-2026-69244 records a High severity (CVSS 7.1) buffer overflow vulnerability in AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response). The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Answer in brief
CVE-2026-69244 records a High severity (CVSS 7.1) buffer overflow vulnerability in AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response). The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
Update aiohttp to 3.14.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBuffer Overflow describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-69244 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| aiohttppip | <=3.14.2 | 3.14.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-69244 records a High severity (CVSS 7.1) buffer overflow vulnerability in AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response). The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for aiohttp.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardUpdate aiohttp to 3.14.3 if you use the affected versions. Test the change in a non-production environment first.
Local check
hol-guard supply-chain scanBuffer Overflow describes the vulnerability class recorded for this advisory. The current record does not mark CVE-2026-69244 as known exploited; continue to monitor the source for status changes. The feed includes package mappings that can be checked against lockfiles and deployed manifests.
| Package | Affected range | Fixed version |
|---|---|---|
| aiohttppip | <=3.14.2 | 3.14.3 |
Fixed versions are reported by the source feed; confirm compatibility before updating.
Reported by GitHub Security Advisories (ghsa).
CVE-2026-69244 records a High severity (CVSS 7.1) buffer overflow vulnerability in AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response). The source record does not mark it as known exploited. 1 affected package is mapped in the feed.
The source record does not mark it as known exploited.
Check lockfiles and deployed manifests for aiohttp.
HOL Guard can help your team review package activity against supported protection paths.
Explore HOL GuardAIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.3, an out-of-bounds heap read could occur in the C response parser while building an error message for a malformed response. An attacker controlled server, or possibly an accidental response, could trigger a DoS in the client. The vulnerable path was error message construction in aiohttp/_http_parser.pyx, where an llhttp error-position pointer was used to build a snippet for malformed chunked responses and malformed request or response bytes at the buffer end. This issue is fixed in version 3.14.3.
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.3, an out-of-bounds heap read could occur in the C response parser while building an error message for a malformed response. An attacker controlled server, or possibly an accidental response, could trigger a DoS in the client. The vulnerable path was error message construction in aiohttp/_http_parser.pyx, where an llhttp error-position pointer was used to build a snippet for malformed chunked responses and malformed request or response bytes at the buffer end. This issue is fixed in version 3.14.3.