How severe is GHSA-63hw-fmq6-xxg2?

No CVSS score has been assigned to GHSA-63hw-fmq6-xxg2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-63hw-fmq6-xxg2?

GHSA-63hw-fmq6-xxg2 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-63hw-fmq6-xxg2?

Update aiohttp to 3.14.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-63hw-fmq6-xxg2 is resolved across your whole dependency graph.

How do I detect GHSA-63hw-fmq6-xxg2 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-63hw-fmq6-xxg2 if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-63hw-fmq6-xxg2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-63hw-fmq6-xxg2 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-63hw-fmq6-xxg2?

GHSA-63hw-fmq6-xxg2 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 45th 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-63hw-fmq6-xxg2?

GHSA-63hw-fmq6-xxg2 is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-63hw-fmq6-xxg2 published, and has it been updated?

GHSA-63hw-fmq6-xxg2 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-63hw-fmq6-xxg2 — aiohttp

Fix: aio-libs/aiohttp@5ab61bb

GHSA-63hw-fmq6-xxg2 is a CWE-770 vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

aiohttp: C HTTP Parser Bypasses max_line_size for Fragmented Lines

Also known asCVE-2026-54277PYSEC-2026-2110

Published

Jun 15, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
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-63hw-fmq6-xxg2.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% 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, it is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. If using the optimised C parser (the default in pre-built wheels), then an attacker may be able to send oversized lines through the HTTP parser and use an excessive amount of memory, potentially leading to DoS. 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.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-63hw-fmq6-xxg2 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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

This vulnerability is rated Moderate because an unauthenticated remote attacker can trigger denial of service against an affected aiohttp HTTP server that uses the default C-based parser, by sending HTTP requests with oversized fragmented lines that bypass max_line_size limits, causing excessive memory consumption.…

Workaround published by Red Hat

Update the aiohttp package to version 3.14.1 or later. Until updated builds are available, reduce exposure by not exposing aiohttp-based HTTP servers directly to untrusted networks. As a workaround, configure aiohttp to use the pure-Python HTTP parser by setting use_cparser=False when creating the application or running the server. This avoids the vulnerable C parser path. Installations that use aiohttp only as an HTTP client are not affected by this flaw.

Source: Red Hat security advisory for GHSA-63hw-fmq6-xxg2 (CC BY 4.0)

Frequently Asked Questions

### Summary It is possible to bypass the max_line_size check in parts of an HTTP request in the C parser. ### Impact If using the optimised C parser (the default in pre-built wheels), then an attacker may be able to send oversized lines through the HTTP parser and use an excessive amount of memory, potentially leading to DoS. ----- Patch: https://github.com/aio-libs/aiohttp/commit/5ab61bb4cd88f19b712f12c7c9295fe262bf804d

O3 Security · Impact-Aware SCA

Is GHSA-63hw-fmq6-xxg2 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works