Is aiohttp affected by CVE-2025-53643?

PyPI aiohttp is affected in <3.12.14.

Is CVE-2025-53643 being exploited?

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

low

CVE-2025-53643

Q: Is CVE-2025-53643 being exploited?

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

PyPI · aiohttp

Summary

AIOHTTP is vulnerable to HTTP Request/Response Smuggling through incorrect parsing of chunked trailer sections

Severity: low
EPSS: 0.3% (p21)
Also known as: GHSA-9548-qrrj-x5pj
Published: 2025-07-14

References

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9548-qrrj-x5pj
https://nvd.nist.gov/vuln/detail/CVE-2025-53643
https://github.com/aio-libs/aiohttp/commit/e8d774f635dc6d1cd3174d0e38891da5de0e2b6a

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.