How severe is GHSA-w2fm-2cpv-w7v5?

No CVSS score has been assigned to GHSA-w2fm-2cpv-w7v5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w2fm-2cpv-w7v5?

GHSA-w2fm-2cpv-w7v5 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-w2fm-2cpv-w7v5?

Update aiohttp to 3.13.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w2fm-2cpv-w7v5 is resolved across your whole dependency graph.

How do I detect GHSA-w2fm-2cpv-w7v5 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-w2fm-2cpv-w7v5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w2fm-2cpv-w7v5?

O3 pinpoints whether GHSA-w2fm-2cpv-w7v5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-w2fm-2cpv-w7v5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-w2fm-2cpv-w7v5 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.

What type of vulnerability is GHSA-w2fm-2cpv-w7v5?

GHSA-w2fm-2cpv-w7v5 is classified as Uncontrolled Resource Consumption (CWE-400), CWE-770 (CWE-770). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-w2fm-2cpv-w7v5 published, and has it been updated?

GHSA-w2fm-2cpv-w7v5 was published on April 1, 2026 and was last updated on July 13, 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

GHSA-w2fm-2cpv-w7v5

Fix: aio-libs/aiohttp@0c2e9da

GHSA-w2fm-2cpv-w7v5 is a Uncontrolled Resource Consumption vulnerability in aiohttp. O3 Security confirms whether GHSA-w2fm-2cpv-w7v5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

aiohttp allows unlimited trailer headers, leading to possible uncapped memory usage

Also known asCVE-2026-22815PYSEC-2026-2094

Published

Apr 1, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Insufficient restrictions in header/trailer handling could cause uncapped memory usage.

Impact

An application could cause memory exhaustion when receiving an attacker controlled request or response. A vulnerable web application could mitigate these risks with a typical reverse proxy configuration.

Patch: https://github.com/aio-libs/aiohttp/commit/0c2e9da51126238a421568eb7c5b53e5b5d17b36

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aiohttp`	all versions	3.13.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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update aiohttp to 3.13.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w2fm-2cpv-w7v5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w2fm-2cpv-w7v5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-w2fm-2cpv-w7v5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Insufficient restrictions in header/trailer handling could cause uncapped memory usage. ### Impact An application could cause memory exhaustion when receiving an attacker controlled request or response. A vulnerable web application could mitigate these risks with a typical reverse proxy configuration. ----- Patch: https://github.com/aio-libs/aiohttp/commit/0c2e9da51126238a421568eb7c5b53e5b5d17b36

O3 Security · Impact-Aware SCA

Is GHSA-w2fm-2cpv-w7v5 in your dependencies?

O3 detects GHSA-w2fm-2cpv-w7v5 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works