Is aiohttp affected by CVE-2026-50269?

PyPI aiohttp is affected in <3.14.0.

Is CVE-2026-50269 being exploited?

Not on the CISA KEV list. EPSS exploit probability is not available.

low

CVE-2026-50269

Q: Is CVE-2026-50269 being exploited?

Not on the CISA KEV list. EPSS exploit probability is not available.

PyPI · aiohttp

Summary

aiohttp: CRLF injection in multipart headers

Severity: low
Also known as: GHSA-m6qw-4cw2-hm4m
Published: 2026-06-15

References

https://github.com/aio-libs/aiohttp/security/advisories/GHSA-m6qw-4cw2-hm4m
https://github.com/aio-libs/aiohttp/commit/bf88077ebb14f4c29924b8e8904cba20c55c28b8
https://github.com/aio-libs/aiohttp

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.