How severe is GHSA-jj3x-wxrx-4x23?

No CVSS score has been assigned to GHSA-jj3x-wxrx-4x23 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jj3x-wxrx-4x23?

GHSA-jj3x-wxrx-4x23 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-jj3x-wxrx-4x23?

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

How do I detect GHSA-jj3x-wxrx-4x23 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-jj3x-wxrx-4x23 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-jj3x-wxrx-4x23 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jj3x-wxrx-4x23 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-jj3x-wxrx-4x23?

GHSA-jj3x-wxrx-4x23 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th 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-jj3x-wxrx-4x23?

GHSA-jj3x-wxrx-4x23 is classified as CWE-835 (CWE-835). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-jj3x-wxrx-4x23 published, and has it been updated?

GHSA-jj3x-wxrx-4x23 was published on January 5, 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 vulnerable to DoS when bypassing assertsGHSA-jj3x-wxrx-4x23

Fix: aio-libs/aiohttp@bc1319e

GHSA-jj3x-wxrx-4x23 is a CWE-835 vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

Also known asCVE-2025-69227PYSEC-2026-1107

Published

Jan 5, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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-jj3x-wxrx-4x23.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs34th percentile — riskier than 34% 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. Versions 3.13.2 and below allow for an infinite loop to occur when assert statements are bypassed, resulting in a DoS attack when processing a POST body. If optimizations are enabled (-O or PYTHONOPTIMIZE=1), and the application includes a handler that uses the Request.post() method, then an attacker may be able to execute a DoS attack with a specially crafted message. This issue is fixed in version 3.13.3.

Affected Packages

1 total 1 fixed

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

Affected Products

1 product · 1 configurations

Application

aiohttpaiohttp

< 3.13.3

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.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jj3x-wxrx-4x23 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 for Red Hat products as it can lead to a Denial of Service (DoS) in applications utilizing the `aiohttp` library. Exploitation requires Python optimizations to be explicitly enabled (e.g., via `-O` or `PYTHONOPTIMIZE=1`) and the application to process POST requests using the…

Workaround published by Red Hat

No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability.

Source: Red Hat security advisory for GHSA-jj3x-wxrx-4x23 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat AI Inference Server 3.2	`rhaiis/vllm-cuda-rhel9:1774351144`	RHSA-2026:5809
Red Hat AI Inference Server 3.2	`rhaiis/model-opt-cuda-rhel9:1774547384`	RHSA-2026:6761
Red Hat AI Inference Server 3.2	`rhaiis/vllm-rocm-rhel9:1775252598`	RHSA-2026:6762
Red Hat Ansible Automation Platform 2.18	`ansible-automation-platform/ee-minimal-rhel8:1786971288`	RHSA-2026:55853
Red Hat Ansible Automation Platform 2.18	`ansible-automation-platform/ee-minimal-rhel9:1786942232`	RHSA-2026:55852
Red Hat Ansible Automation Platform 2.5	`ansible-automation-platform-25/lightspeed-rhel8:1777403872`	RHSA-2026:13553
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/lightspeed-chatbot-rhel9:1777398576`	RHSA-2026:13545
Red Hat Ansible Automation Platform 2.6	`ansible-automation-platform-26/lightspeed-rhel9:1787244079`	RHSA-2026:59155

Frequently Asked Questions

### Summary When assert statements are bypassed, an infinite loop can occur, resulting in a DoS attack when processing a POST body. ### Impact If optimisations are enabled (`-O` or `PYTHONOPTIMIZE=1`), and the application includes a handler that uses the `Request.post()` method, then an attacker may be able to execute a DoS attack with a specially crafted message. ------ Patch: https://github.com/aio-libs/aiohttp/commit/bc1319ec3cbff9438a758951a30907b072561259

O3 Security · Impact-Aware SCA

Is GHSA-jj3x-wxrx-4x23 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works