How severe is GHSA-m6qw-4cw2-hm4m?

No CVSS score has been assigned to GHSA-m6qw-4cw2-hm4m yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m6qw-4cw2-hm4m?

GHSA-m6qw-4cw2-hm4m affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-m6qw-4cw2-hm4m?

Update aiohttp to 3.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6qw-4cw2-hm4m is resolved across your whole dependency graph.

How do I detect GHSA-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m?

O3 pinpoints whether GHSA-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m actively exploited in the wild?

No public exploit code has been indexed for GHSA-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m?

GHSA-m6qw-4cw2-hm4m is classified as CWE-93 (CWE-93), CWE-113 (CWE-113). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-m6qw-4cw2-hm4m published, and has it been updated?

GHSA-m6qw-4cw2-hm4m was published on June 15, 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

Not in CISA KEV

GHSA-m6qw-4cw2-hm4m

Fix: aio-libs/aiohttp@bf88077

GHSA-m6qw-4cw2-hm4m is a CWE-93 vulnerability in aiohttp. O3 Security confirms whether GHSA-m6qw-4cw2-hm4m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

aiohttp: CRLF injection in multipart headers

Also known asCVE-2026-50269PYSEC-2026-2106

Published

Jun 15, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 13, 2026 · OSV.dev, NVD, 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

Attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar.

Impact

In the unlikely situation that an application is passing user-controlled strings into MultipartWriter.append(headers=...) or Payload.headers, then an attacker may be able to modify the request to inject headers or change the contents of the request.

Workaround

Sanitise such user input.

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`aiohttp`	all versions	3.14.0

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.14.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m 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-m6qw-4cw2-hm4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Attacker-controlled input included into multipart/payload headers can be used to modify a request to inject additional headers or similar. ### Impact In the unlikely situation that an application is passing user-controlled strings into `MultipartWriter.append(headers=...)` or `Payload.headers`, then an attacker may be able to modify the request to inject headers or change the contents of the request. ### Workaround Sanitise such user input. ----- Patch: https://github.com/aio-libs/aiohttp/commit/bf88077ebb14f4c29924b8e8904cba20c55c28b8

O3 Security · Impact-Aware SCA

Is GHSA-m6qw-4cw2-hm4m in your dependencies?

O3 detects GHSA-m6qw-4cw2-hm4m 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