How severe is GHSA-2g87-pp6c-29x5?

No CVSS score has been assigned to GHSA-2g87-pp6c-29x5 yet. Review the advisory details and affected package list to assess your exposure.

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

GHSA-2g87-pp6c-29x5 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

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

Update aiohttp to 3.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g87-pp6c-29x5 is resolved across your whole dependency graph.

How do I detect GHSA-2g87-pp6c-29x5 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-2g87-pp6c-29x5 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-2g87-pp6c-29x5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2g87-pp6c-29x5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-2g87-pp6c-29x5 published, and has it been updated?

GHSA-2g87-pp6c-29x5 was published on October 19, 2026 and was last updated on October 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

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

Fix: aio-libs/aiohttp@09bcaa7

GHSA-2g87-pp6c-29x5 is a security vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

Published

Oct 19, 2026

Updated

Oct 19, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 19, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍aiohttp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aiohttp`	all versions	3.14.4`pip install --upgrade 'aiohttp==3.14.4'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aiohttp to 3.14.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2g87-pp6c-29x5 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-2g87-pp6c-29x5 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works