VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aiohttp-session: vulnerability history, versions and safety

aiohttp-session is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 24 releases, from Jun 2018 to Dec 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aiohttp-session vulnerabilities

Vulert verdict on aiohttp-session 2.12.1 i

Updated on 23 Oct 2026

Good news: 2.12.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 4.

Package health score 72/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Quiet

What to do: Stay on 2.12.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 2.12.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 2.12.1 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 20 Dec 2018 i
  • Highest CVSS 6.5 i
  • With no published fix 0 i
  • Depended on by 59 packages i
  • Stars 245 i
  • OpenSSF scorecard 5/10 i
  • Last release 24 months ago i
  • Licence Apache-2.0 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-session, 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
2.12.1 25 Sep 2024 none Apache-2.0 — Details →
2.12.0 28 Oct 2022 none Apache-2.0 — Details →
2.11.0 31 Jan 2022 none Apache-2.0 — Details →
2.10.0 30 Dec 2021 none Apache-2.0 — Details →
2.10.0a0 04 Nov 2021 none Apache-2.0 — Details →
2.9.0 04 Nov 2019 none Apache-2.0 — Details →
2.8.0 17 Sep 2019 none Apache-2.0 — Details →
2.7.0 12 Oct 2018 none Apache-2.0 — Details →
2.6.0 12 Sep 2018 H1 U1 Apache-2.0 Yes Details →
2.5.1 12 May 2018 H1 U1 Apache-2.0 Yes Details →
2.4.0 04 May 2018 H1 U1 Apache-2.0 Yes Details →
2.3.0 13 Feb 2018 H2 U2 Apache-2.0 Yes Details →
2.2.0 31 Jan 2018 H2 U2 Apache-2.0 Yes Details →
2.1.0 24 Nov 2017 H2 U2 Apache-2.0 Yes Details →
2.0.1 22 Nov 2017 H2 U2 Apache-2.0 Yes Details →
2.0.0 21 Nov 2017 H2 U2 Apache-2.0 Yes Details →
1.2.1 20 Nov 2017 H2 U2 Apache-2.0 Yes Details →
1.2.0 06 Nov 2017 H2 U2 Apache-2.0 Yes Details →
1.1.0 03 Nov 2017 H2 U2 Apache-2.0 Yes Details →
1.0.1 13 Sep 2017 H2 U2 Apache-2.0 Yes Details →
1.0.0 27 Jul 2017 H2 U2 Apache-2.0 Yes Details →
0.8.0 04 Dec 2016 H2 U2 Apache-2.0 Yes Details →
0.7.1 24 Oct 2016 H2 U2 Apache-2.0 Yes Details →
0.7.0 24 Sep 2016 H2 U2 Apache-2.0 Yes Details →
0.5.0 21 Feb 2016 H2 U2 Apache-2.0 Yes Details →
0.4.0 05 Jan 2016 H2 U2 Apache-2.0 Yes Details →
0.3.0 20 Nov 2015 H2 U2 Apache-2.0 Yes Details →
0.2.0 07 Sep 2015 H2 U2 Apache-2.0 Yes Details →
0.1.2 07 Aug 2015 H2 U2 Apache-2.0 Yes Details →
0.1.1 20 Apr 2015 H2 U2 Apache-2.0 Yes Details →
0.1.0 13 Apr 2015 H2 U2 Apache-2.0 Yes Details →
0.0.1 01 Apr 2015 H2 U2 Apache-2.0 Yes Details →

All 32 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 4

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

03 Vulnerabilities

Recorded vulnerabilities for aiohttp-session

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-1000519: aiohttp-session Session Fixation vulnerability 6.5 high 2.4.0 13 Sep 2018
CVE-2018-1000814: aiohttp-session - Non-expiring sessions / Infinite lifespan 6.5 high 2.7.0 20 Dec 2018
CVE-2018-1000814: aiohttp-session Non-expiring sessions / Infinite lifespan N/A unrated 2.7.0 20 Dec 2018
CVE-2018-1000519: aiohttp-session Session Fixation Vulnerability N/A unrated 2.4.0 26 Jun 2018

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-session

Is aiohttp-session safe to use?

Vulert records 4 vulnerabilities for aiohttp-session in PyPI: 0 critical, 2 high, 0 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is aiohttp-session's Vulert package health score?

Vulert scores aiohttp-session 72/100, which reads as in good shape. 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).

Is the latest version of aiohttp-session affected?

No. 2.12.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of aiohttp-session should I use?

2.12.1 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-session have?

4 vulnerabilities are recorded for aiohttp-session in the PyPI ecosystem: 0 critical, 2 high, 0 medium and 0 low, plus 2 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-session vulnerabilities disclosed?

0 vulnerabilities were recorded for aiohttp-session in the last 12 months, and the oldest entry in this database dates to 26 Jun 2018. 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-session 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-session for upcoming vulnerabilities?

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