VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aiohttp: vulnerability history, versions and safety

aiohttp is a package in the PyPI ecosystem. Vulert records 104 vulnerabilities for it across 120 releases, from Feb 2021 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
104 vulnerabilities recorded H7 M30 L20 U47
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
78 in the last 12 months

Most recent disclosure 20 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aiohttp vulnerabilities

Vulert verdict on aiohttp 3.14.5 i

Updated on 23 Oct 2026

Careful: 3.14.5 has 4 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.14.5 — affected i
  • Vulnerabilities on record 104 over 5 years · 78 in the last year i
  • Latest disclosure 20 Oct 2026 i
  • Highest CVSS 8.7 i
  • With no published fix 2 i
  • Depended on by 47,315 packages i
  • Stars 16,583 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 AND MIT i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for aiohttp, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.14.5 11 Oct 2026 M1 U3 Apache-2.0 AND MIT No Details →
3.14.4 05 Oct 2026 M1 U3 Apache-2.0 AND MIT No Details →
3.14.3 23 Jul 2026 H3 M3 L2 Apache-2.0 AND MIT Yes Details →
3.14.2 20 Jul 2026 H4 M3 L2 U1 Apache-2.0 AND MIT Yes Details →
3.14.1 07 Jun 2026 H4 M5 L2 U3 Apache-2.0 AND MIT Yes Details →
3.14.0 01 Jun 2026 H4 M10 L5 U11 Apache-2.0 AND MIT Yes Details →
3.13.5 31 Mar 2026 H4 M12 L6 U14 Apache-2.0 AND MIT Yes Details →
3.13.4 28 Mar 2026 H4 M12 L6 U14 Apache-2.0 AND MIT Yes Details →
3.13.3 03 Jan 2026 H4 M16 L12 U24 Apache-2.0 AND MIT Yes Details →
3.13.2 28 Oct 2025 H5 M19 L16 U32 Apache-2.0 AND MIT Yes Details →
3.13.1 17 Oct 2025 H5 M19 L16 U32 Apache-2.0 AND MIT Yes Details →
3.13.0 06 Oct 2025 H5 M19 L16 U32 Apache-2.0 AND MIT Yes Details →
3.12.15 29 Jul 2025 H5 M19 L16 U32 Apache-2.0 AND MIT Yes Details →
3.12.14 10 Jul 2025 H5 M19 L16 U32 Apache-2.0 Yes Details →
3.12.13 14 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.12 10 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.11 07 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.10 07 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.9 04 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.8 04 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.7 02 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.7rc0 02 Jun 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.6 31 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.4 29 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.3 28 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.2 27 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.1 26 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.1rc0 26 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0 24 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0rc1 24 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0rc0 24 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0b3 22 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0b2 22 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0b1 22 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.12.0b0 20 May 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.18 21 Apr 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.17 19 Apr 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.16 02 Apr 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.15 01 Apr 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.14 17 Mar 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.13 24 Feb 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.12 06 Feb 2025 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.11 18 Dec 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.10 05 Dec 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.9 01 Dec 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.8 27 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.7 21 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.6 19 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.5 19 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.4 19 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.3 19 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.2 14 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.1 14 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0 13 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.10.11 13 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0rc2 13 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.10.11rc0 13 Nov 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.11.0rc1 11 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0rc0 10 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b5 10 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b4 08 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b3 06 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b2 03 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b1 02 Nov 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.11.0b0 29 Oct 2024 H5 M19 L18 U33 Apache-2.0 Yes Details →
3.10.10 10 Oct 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.9 04 Oct 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.8 28 Sep 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.7 27 Sep 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.6 24 Sep 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.6rc2 24 Sep 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.6rc1 23 Sep 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.6rc0 23 Sep 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.5 19 Aug 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.4 17 Aug 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.3 10 Aug 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.2 08 Aug 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.10.1 04 Aug 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.0 30 Jul 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.0rc0 29 Jul 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.10.0b1 22 Jul 2024 H5 M21 L18 U35 Apache-2.0 Yes Details →
3.9.5 16 Apr 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.9.4 11 Apr 2024 H5 M20 L18 U34 Apache-2.0 Yes Details →
3.9.4rc0 16 Feb 2024 H6 M21 L18 U37 Apache-2.0 No Details →
3.9.3 29 Jan 2024 H6 M21 L18 U37 Apache-2.0 No Details →
3.9.2 28 Jan 2024 H6 M21 L18 U37 Apache-2.0 No Details →
3.9.1 26 Nov 2023 H7 M22 L18 U39 Apache-2.0 No Details →
3.9.0 18 Nov 2023 H7 M22 L18 U39 Apache-2.0 No Details →
3.9.0rc0 14 Nov 2023 H7 M24 L18 U41 Apache-2.0 No Details →
3.9.0b1 06 Nov 2023 H7 M24 L18 U41 Apache-2.0 No Details →
3.9.0b0 07 Oct 2023 H7 M24 L18 U41 Apache-2.0 No Details →
3.8.6 07 Oct 2023 H7 M24 L18 U41 Apache-2.0 No Details →
3.8.5 19 Jul 2023 H7 M26 L18 U42 Apache-2.0 No Details →
3.8.4 12 Feb 2023 H7 M27 L18 U43 Apache-2.0 No Details →
3.8.3 21 Sep 2022 H7 M27 L18 U43 Apache-2.0 No Details →
3.8.2 21 Sep 2022 H7 M27 L18 U43 Apache-2.0 No Details →
3.8.1 14 Nov 2021 H7 M28 L18 U43 Apache-2.0 No Details →
3.8.0 31 Oct 2021 H7 M28 L18 U43 Apache-2.0 No Details →
3.8.0b0 31 Oct 2021 H7 M28 L19 U44 Apache-2.0 No Details →
3.8.0a7 30 Oct 2021 H7 M28 L19 U44 Apache-2.0 No Details →
3.7.4.post0 06 Mar 2021 H7 M28 L19 U44 — No Details →
3.7.4 25 Feb 2021 H7 M28 L19 U44 — No Details →
3.7.3 18 Nov 2020 H7 M28 L20 U45 — No Details →
3.7.2 27 Oct 2020 H7 M28 L20 U45 — No Details →
3.7.1 25 Oct 2020 H7 M28 L20 U45 — No Details →
3.7.0 24 Oct 2020 H7 M28 L20 U45 — No Details →
3.7.0b1 22 Oct 2020 H7 M28 L20 U45 — No Details →
3.7.0b0 21 Oct 2020 H7 M28 L20 U45 — No Details →
3.6.3 12 Oct 2020 H7 M28 L20 U45 — No Details →
3.6.2 09 Oct 2019 H7 M28 L20 U45 — No Details →
3.6.2a2 09 Oct 2019 H7 M28 L20 U45 — No Details →
3.6.2a1 09 Oct 2019 H7 M28 L20 U45 — No Details →
3.6.2a0 09 Oct 2019 H7 M28 L20 U45 — No Details →
4.0.0a1 09 Oct 2019 U1 — No Details →
3.6.1 19 Sep 2019 H7 M28 L20 U45 — No Details →
3.6.1b4 17 Sep 2019 H7 M28 L20 U45 — No Details →
3.6.1b3 15 Sep 2019 H7 M28 L20 U45 — No Details →
3.6.0 06 Sep 2019 H7 M28 L20 U45 — No Details →
3.6.0b0 05 Sep 2019 H7 M28 L20 U45 — No Details →
3.6.0a12 29 Aug 2019 H7 M28 L20 U45 — No Details →

The newest 120 of 315 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2022 2
  • 2023 11
  • 2024 9
  • 2025 2
  • 2026 78

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 78 of the 104 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for aiohttp

The 5 most severe of 104 vulnerabilities recorded for this package

Search all 104 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Excessive Resource Consumption in aiohttp: A Critical Vulnerability 8.7 high 3.14.4 19 Oct 2026
CVE-2026-111066: AIOHTTP File Descriptor Exhaustion in Multipart Requests 8.2 high 3.14.4 20 Oct 2026
CVE-2026-111064: aiohttp Server Lacks Initial Request/Header Timeout 8.2 high 3.14.4 19 Oct 2026
CVE-2026-54275: AIOHTTP Server Hostname TLS SNI Check Bypass Vulnerability 7.5 high 3.14.1 22 Jun 2026
CVE-2024-52303: aiohttp Memory Leak Vulnerability Due to Middleware Misconfiguration 7.5 high 3.10.11 07 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About aiohttp

Is aiohttp safe to use?

Vulert records 104 vulnerabilities for aiohttp in PyPI: 0 critical, 7 high, 30 medium and 20 low, plus 47 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is aiohttp's Vulert package health score?

Vulert scores aiohttp 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of aiohttp affected?

Yes. 3.14.5, the version you would install today, has 4 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of aiohttp should I use?

3.14.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does aiohttp have?

104 vulnerabilities are recorded for aiohttp in the PyPI ecosystem: 0 critical, 7 high, 30 medium and 20 low, plus 47 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new aiohttp vulnerabilities disclosed?

78 vulnerabilities were recorded for aiohttp in the last 12 months, and the oldest entry in this database dates to 26 Feb 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of aiohttp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor aiohttp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the aiohttp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.