How severe is GHSA-2vrm-gr82-f7m5?

No CVSS score has been assigned to GHSA-2vrm-gr82-f7m5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2vrm-gr82-f7m5?

GHSA-2vrm-gr82-f7m5 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-2vrm-gr82-f7m5?

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

How do I detect GHSA-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5?

O3 pinpoints whether GHSA-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5?

GHSA-2vrm-gr82-f7m5 is classified as CWE-113 (CWE-113). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-2vrm-gr82-f7m5 published, and has it been updated?

GHSA-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5

Fix: aio-libs/aiohttp@9a6ada9

GHSA-2vrm-gr82-f7m5 is a CWE-113 vulnerability in aiohttp. O3 Security confirms whether GHSA-2vrm-gr82-f7m5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

AIOHTTP has CRLF injection through multipart part content type header construction

Also known asCVE-2026-34514PYSEC-2026-2096

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

An attacker who controls the content_type parameter in aiohttp could use this to inject extra headers or similar exploits.

Impact

If an application allows untrusted data to be used for the multipart content_type parameter when constructing a request, an attacker may be able to manipulate the request to send something other than what the developer intended.

Patch: https://github.com/aio-libs/aiohttp/commit/9a6ada97e2c6cf1ce31727c6c9fcea17c21f6f06

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-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5 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-2vrm-gr82-f7m5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary An attacker who controls the `content_type` parameter in aiohttp could use this to inject extra headers or similar exploits. ### Impact If an application allows untrusted data to be used for the multipart `content_type` parameter when constructing a request, an attacker may be able to manipulate the request to send something other than what the developer intended. ----- Patch: https://github.com/aio-libs/aiohttp/commit/9a6ada97e2c6cf1ce31727c6c9fcea17c21f6f06

O3 Security · Impact-Aware SCA

Is GHSA-2vrm-gr82-f7m5 in your dependencies?

O3 detects GHSA-2vrm-gr82-f7m5 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