How severe is GHSA-9x8q-7h8h-wcw9?

No CVSS score has been assigned to GHSA-9x8q-7h8h-wcw9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-9x8q-7h8h-wcw9?

GHSA-9x8q-7h8h-wcw9 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-9x8q-7h8h-wcw9?

Update aiohttp to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x8q-7h8h-wcw9 is resolved across your whole dependency graph.

How do I detect GHSA-9x8q-7h8h-wcw9 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-9x8q-7h8h-wcw9 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-9x8q-7h8h-wcw9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-9x8q-7h8h-wcw9 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-9x8q-7h8h-wcw9?

GHSA-9x8q-7h8h-wcw9 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 37th 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-9x8q-7h8h-wcw9?

GHSA-9x8q-7h8h-wcw9 is classified as CWE-404 (CWE-404). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-9x8q-7h8h-wcw9 published, and has it been updated?

GHSA-9x8q-7h8h-wcw9 was published on June 15, 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

GHSA-9x8q-7h8h-wcw9 — aiohttp

Fix: aio-libs/aiohttp@a762eda

GHSA-9x8q-7h8h-wcw9 is a CWE-404 vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

aiohttp: Payload Response Resources Are Not Closed After Mid-Body Disconnect

Also known asCVE-2026-54280PYSEC-2026-2113

Published

Jun 15, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 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-9x8q-7h8h-wcw9.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs37th percentile — riskier than 37% 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

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.1, payload resources are not closed correctly when a client disconnects in the middle of a write. If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. This vulnerability is fixed in 3.14.1.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

aiohttpaiohttp

≥ 3.12.1 && < 3.14.1

range

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.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9x8q-7h8h-wcw9 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.

Frequently Asked Questions

### Summary Payload resources are not closed correctly when a client disconnects in the middle of a write. ### Impact If a payload is using an open file or similar limited resource, then an attacker may be able to cause resource starvation temporarily until garbage collection or similar closes the file. ----- Patch: https://github.com/aio-libs/aiohttp/commit/a762eda5242f6490d6ba667533193f8b473ad587

O3 Security · Impact-Aware SCA

Is GHSA-9x8q-7h8h-wcw9 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works