How severe is GHSA-mwh4-6h8g-pg8w?

No CVSS score has been assigned to GHSA-mwh4-6h8g-pg8w yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mwh4-6h8g-pg8w?

GHSA-mwh4-6h8g-pg8w affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-mwh4-6h8g-pg8w?

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

How do I detect GHSA-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w?

O3 pinpoints whether GHSA-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w actively exploited in the wild?

No public exploit code has been indexed for GHSA-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w?

GHSA-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w published, and has it been updated?

GHSA-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w

GHSA-mwh4-6h8g-pg8w is a CWE-113 vulnerability in aiohttp. O3 Security confirms whether GHSA-mwh4-6h8g-pg8w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

AIOHTTP has HTTP response splitting via \r in reason phrase

Also known asCVE-2026-34519PYSEC-2026-2101

Published

Apr 1, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

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 reason parameter when creating a Response may be able to inject extra headers or similar exploits.

Impact

In the unlikely situation that an application allows untrusted data to be used in the response's reason parameter, then an attacker could manipulate the response to send something different from what the developer intended.

Patch: https://github.com/aio-libs/aiohttp/commit/53b35a2f8869c37a133e60bf1a82a1c01642ba2b

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-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w 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-mwh4-6h8g-pg8w. 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 `reason` parameter when creating a `Response` may be able to inject extra headers or similar exploits. ### Impact In the unlikely situation that an application allows untrusted data to be used in the response's `reason` parameter, then an attacker could manipulate the response to send something different from what the developer intended. ----- Patch: https://github.com/aio-libs/aiohttp/commit/53b35a2f8869c37a133e60bf1a82a1c01642ba2b

O3 Security · Impact-Aware SCA

Is GHSA-mwh4-6h8g-pg8w in your dependencies?

O3 detects GHSA-mwh4-6h8g-pg8w 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