How severe is GHSA-mq44-7p77-q5h7?

No CVSS score has been assigned to GHSA-mq44-7p77-q5h7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mq44-7p77-q5h7?

GHSA-mq44-7p77-q5h7 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-mq44-7p77-q5h7?

Update aiohttp to 3.14.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mq44-7p77-q5h7 is resolved across your whole dependency graph.

How do I detect GHSA-mq44-7p77-q5h7 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-mq44-7p77-q5h7 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.

Is GHSA-mq44-7p77-q5h7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mq44-7p77-q5h7 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 is the EPSS score for GHSA-mq44-7p77-q5h7?

GHSA-mq44-7p77-q5h7 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-mq44-7p77-q5h7?

GHSA-mq44-7p77-q5h7 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mq44-7p77-q5h7 published, and has it been updated?

GHSA-mq44-7p77-q5h7 was published on August 3, 2026 and was last updated on September 10, 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: WebSocket client accepts compressed frames without negotiated permessage-deflateGHSA-mq44-7p77-q5h7

Fix: aio-libs/aiohttp#12978

GHSA-mq44-7p77-q5h7 is a Improper Input Validation vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

Also known asCVE-2026-59881PYSEC-2026-3547

Published

Aug 3, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mq44-7p77-q5h7.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

The client accepts and decompresses frames with the RSV1 bit set even when the permessage-deflate extension was not negotiated.

Impact

A client may unexpectedly decompress WebSocket frames when explicitly opted out. This could lead to additional CPU/memory consumption, but is unlikely to be a significant issue unless a zip bomb vulnerability or similar is also present.

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

Affected Packages

1 total 1 fixed

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

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.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mq44-7p77-q5h7 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Red Hat rates this flaw as Moderate with a CVSS score of 5.3 because exploitation requires an aiohttp WebSocket client to connect to an attacker-controlled server. In typical Red Hat product deployments, aiohttp serves as an HTTP client library for internal service communication rather than establishing WebSocket…

Workaround published by Red Hat

For deployments where upgrading is not immediately possible, ensure that aiohttp WebSocket clients only connect to trusted servers. The vulnerability requires the client to have opted out of permessage-deflate compression and the server to send RSV1-flagged frames, so connections using default compression settings are less likely to trigger this issue.

Source: Red Hat security advisory for GHSA-mq44-7p77-q5h7 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AI Inference Server 3.2	`rhaiis/model-opt-cuda-rhel9:1790621714`	RHSA-2026:73859
Red Hat AI Inference Server 3.2	`rhaiis/vllm-cuda-rhel9:1790621718`	RHSA-2026:73929
Red Hat AI Inference Server 3.2	`rhaiis/vllm-rocm-rhel9:1790621713`	RHSA-2026:73930
Red Hat AI Inference Server 3.4	`rhaii/vllm-cpu-rhel9:1790075793`	RHSA-2026:70965
Red Hat AI Inference Server 3.4	`rhaii/vllm-spyre-rhel9:1790076141`	RHSA-2026:70969
Red Hat AI Inference Server 3.4	`rhaii/vllm-cuda-rhel9:1790090131`	RHSA-2026:70979
Red Hat AI Inference Server 3.4	`rhaii/vllm-rocm-rhel9:1790109620`	RHSA-2026:70995

Frequently Asked Questions

### Summary The client accepts and decompresses frames with the RSV1 bit set even when the `permessage-deflate` extension was not negotiated. ### Impact A client may unexpectedly decompress WebSocket frames when explicitly opted out. This could lead to additional CPU/memory consumption, but is unlikely to be a significant issue unless a zip bomb vulnerability or similar is also present. --- Patch: https://github.com/aio-libs/aiohttp/commit/47fb6ae354d4fa22048f4dbe7dbf82b625f0a2f6