How severe is GHSA-54jq-c3m8-4m76?

No CVSS score has been assigned to GHSA-54jq-c3m8-4m76 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-54jq-c3m8-4m76?

GHSA-54jq-c3m8-4m76 affects the following packages: aiohttp (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-54jq-c3m8-4m76?

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

How do I detect GHSA-54jq-c3m8-4m76 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-54jq-c3m8-4m76 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-54jq-c3m8-4m76?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-54jq-c3m8-4m76 can be triaged on real exposure rather than presence alone.

Is GHSA-54jq-c3m8-4m76 actively exploited in the wild?

No public exploit code has been indexed for GHSA-54jq-c3m8-4m76 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-54jq-c3m8-4m76?

GHSA-54jq-c3m8-4m76 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 27th 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-54jq-c3m8-4m76?

GHSA-54jq-c3m8-4m76 is classified as Path Traversal (CWE-22), Information Exposure (CWE-200). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-54jq-c3m8-4m76 published, and has it been updated?

GHSA-54jq-c3m8-4m76 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

GHSA-54jq-c3m8-4m76 — aiohttp

Fix: aio-libs/aiohttp@f2a86fd

GHSA-54jq-c3m8-4m76 is a Path Traversal vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below.

AIOHTTP vulnerable to brute-force leak of internal static ﬁle path components

Also known asCVE-2025-69226PYSEC-2026-1097

Published

Jan 5, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 25, 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-54jq-c3m8-4m76.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs27th percentile — riskier than 27% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 enable an attacker to ascertain the existence of absolute path components through the path normalization logic for static files meant to prevent path traversal. If an application uses web.static() (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components. 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'`

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-54jq-c3m8-4m76 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-54jq-c3m8-4m76 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-54jq-c3m8-4m76. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

UbuntuMEDIUM

USN-8032-1Ubuntu

Frequently Asked Questions

### Summary Path normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the existence of absolute path components. ### Impact If an application uses `web.static()` (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components. ------ Patch: https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e

O3 Security · Impact-Aware SCA

Is GHSA-54jq-c3m8-4m76 in your dependencies?

O3 Security finds GHSA-54jq-c3m8-4m76 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works