LowGHSA-54jq-c3m8-4m76CVE-2025-69226PYSEC-2026-1097

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

Published 5 Jan 2026 · Updated 10 Sept 2026

Is your project on an affected aiohttp?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<3.13.3
Fixed in
3.13.3
Update to the fixed version for your release line, for example:pip install 'aiohttp>=3.13.3'

Details

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

Is GHSA-54jq-c3m8-4m76 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected aiohttp, and gives you the command that fixes it.

More advisories for aiohttp

  • HighCVE-2026-128124AIOHTTP: Event loop stall in add_domain() wildcard matching · 16 Nov 2026
  • MediumCVE-2026-128125AIOHTTP: Unbounded cookie storage in client CookieJar · 16 Nov 2026
  • HighCVE-2026-128126AIOHTTP: Too many URL-encoded form fields block the event loop · 16 Nov 2026
  • HighCVE-2026-128127AIOHTTP: Base64 multipart parts bypass client_max_size · 16 Nov 2026
  • HighCVE-2026-128128AIOHTTP: WebSocket max_msg_size bypass via integer overflow · 16 Nov 2026
  • HighCVE-2026-128129AIOHTTP: Unbounded buffering of data received during an upgrade request · 16 Nov 2026
All 64 advisories for aiohttp

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.