# GHSA-2g87-pp6c-29x5: aiohttp: Multiple instances of excessive or unbounded memory/CPU use

> Attackers can cause resource exhaustion via specially crafted requests, leading to denial of service in applications using the aiohttp library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026

## What is GHSA-2g87-pp6c-29x5?

GHSA-2g87-pp6c-29x5 is a denial of service vulnerability in aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary

Multiple cases were found where aiohttp could use excessive or unbounded memory, or excessive CPU consumption on attacker controlled requests.

### Impact

An attacker could cause resource exhaustion through specially crafted requests.

## Which versions are affected by GHSA-2g87-pp6c-29x5?

2 open source packages ship an affected version, including aiohttp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aiohttp` | PyPI | All versions | 3.14.4 |
| `aiohttp` | PyPI | All versions | 3.14.4 |

## How do I fix GHSA-2g87-pp6c-29x5?

Upgrade aiohttp to 3.14.4 or later.

## Is GHSA-2g87-pp6c-29x5 being exploited?

There is no known exploitation of GHSA-2g87-pp6c-29x5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-2g87-pp6c-29x5 and fix it if it is affected.

What it is: GHSA-2g87-pp6c-29x5 is a denial of service vulnerability in aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-2g87-pp6c-29x5 in the wild and no public exploit code.

Affected packages and fixed versions:
- aiohttp (PyPI): affected all versions; fixed in 3.14.4
- aiohttp (PyPI): affected all versions; fixed in 3.14.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-2g87-pp6c-29x5/ (Markdown: https://insights.sbomify.com/GHSA-2g87-pp6c-29x5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-2g87-pp6c-29x5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-2g87-pp6c-29x5/
Summaries are generated and may contain mistakes; the official description above is the record.