Is aiohttp affected by CVE-2025-69226?

PyPI aiohttp is affected in <3.13.3.

Is CVE-2025-69226 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.3%.

low

CVE-2025-69226

Q: Is CVE-2025-69226 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.3%.

PyPI · aiohttp

Summary

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

Severity: low
EPSS: 0.3% (p23)
Also known as: GHSA-54jq-c3m8-4m76
Published: 2026-01-05

References

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-54jq-c3m8-4m76
https://nvd.nist.gov/vuln/detail/CVE-2025-69226
https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e

Related advisories

CVE-2025-69223 — high · PyPI/aiohttp
CVE-2026-54274 — medium · PyPI/aiohttp
CVE-2026-54273 — medium · PyPI/aiohttp
CVE-2026-54278 — medium · PyPI/aiohttp
CVE-2026-54277 — medium · PyPI/aiohttp
CVE-2026-54276 — medium · PyPI/aiohttp
CVE-2026-47265 — medium · PyPI/aiohttp
CVE-2026-34993 — medium · PyPI/aiohttp

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.