VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

hyperkitty: vulnerability history, versions and safety

hyperkitty is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 32 releases, from May 2021 to Jun 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
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 hyperkitty vulnerabilities

Vulert verdict on hyperkitty 1.3.12 i

Updated on 23 Oct 2026

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

Package health score 72/100
  • Security No known security issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

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

  • Current release 1.3.12 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 01 Jun 2021 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 1 packages i
  • Stars 228 i
  • Last release 25 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 hyperkitty, 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
1.3.12 21 Sep 2024 none GPL-3.0 — Details →
1.3.12a1 01 Sep 2024 none GPL-3.0 — Details →
1.3.11 03 Jul 2024 none GPL-3.0 — Details →
1.3.10 22 Jun 2024 none GPL-3.0 — Details →
1.3.9 27 Feb 2024 none GPL-3.0 — Details →
1.3.8 21 Oct 2023 none GPL-3.0 — Details →
1.3.7 04 Jan 2023 none GPL-3.0 — Details →
1.3.6 22 Oct 2022 none GPL-3.0 — Details →
1.3.5 13 Oct 2021 none GPL-3.0 — Details →
1.3.4 03 Feb 2021 H1 U1 GPL-3.0 Yes Details →
1.3.4rc2 17 Jan 2021 H1 U1 GPL-3.0 Yes Details →
1.3.4rc1 16 Jan 2021 H1 U1 GPL-3.0 Yes Details →
1.3.3 02 Jun 2020 H1 U1 GPL-3.0 Yes Details →
1.3.3rc2 23 May 2020 H1 U1 GPL-3.0 Yes Details →
1.3.3rc1 10 May 2020 H1 U1 GPL-3.0 Yes Details →
1.3.2 13 Jan 2020 H1 U1 GPL-3.0 Yes Details →
1.3.1 09 Dec 2019 H1 U1 GPL-3.0 Yes Details →
1.3.0 05 Sep 2019 H1 U1 GPL-3.0 Yes Details →
1.2.2 22 Feb 2019 H1 U1 GPL-3.0 Yes Details →
1.2.1 31 Aug 2018 H1 U1 GPL-3.0 Yes Details →
1.2.0 11 Jul 2018 H1 U1 GPL-3.0 Yes Details →
1.2.0a1 11 Mar 2018 H1 U1 GPL-3.0 Yes Details →
1.1.4 09 Oct 2017 H1 U1 GPL-3.0 Yes Details →
1.1.1 04 Aug 2017 H1 U1 GPL-3.0 Yes Details →
1.1.0 26 May 2017 H1 U1 GPL-3.0 Yes Details →
1.0.3 15 Nov 2015 H1 U1 GPL-3.0 Yes Details →
1.0.2 29 Sep 2015 H1 U1 GPL-3.0 Yes Details →
1.0.1 07 May 2015 H1 U1 GPL-3.0 Yes Details →
1.0.0 28 Apr 2015 H1 U1 GPL-3.0 Yes Details →
1.0.0rc1 18 Apr 2015 H1 U1 GPL-3.0 Yes Details →
0.9.7 14 Apr 2015 H1 U1 GPL-3.0 Yes Details →
0.9.6 16 Mar 2015 H1 U1 GPL-3.0 Yes Details →
0.9.3 12 Jun 2014 H1 U1 GPL-3.0 Yes Details →
0.1.7 14 Feb 2014 H1 U1 GPL-3.0 Yes Details →
0.1.6 26 Jul 2013 H1 U1 GPL-3.0 Yes Details →
0.1.5 18 May 2013 H1 U1 GPL-3.0 Yes Details →
0.1.4 21 Feb 2013 H1 U1 GPL-3.0 Yes Details →
0.1.3 10 Dec 2012 H1 U1 GPL-3.0 Yes Details →
0.1.2 26 Nov 2012 H1 U1 GPL-3.0 Yes Details →
0.1.1 22 Nov 2012 H1 U1 GPL-3.0 Yes Details →
0.1.0 21 Nov 2012 H1 U1 GPL-3.0 Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2

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

03 Vulnerabilities

Recorded vulnerabilities for hyperkitty

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-33038: HyperKitty - Exposure of Sensitive Information 7.5 high 1.3.5 01 Jun 2021
CVE-2021-33038: HyperKitty - Public Visibility of Private Mailing List Archives during Import N/A unrated 1.3.5 26 May 2021

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 hyperkitty

Is hyperkitty safe to use?

Vulert records 2 vulnerabilities for hyperkitty in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 hyperkitty's Vulert package health score?

Vulert scores hyperkitty 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 hyperkitty affected?

No. 1.3.12, 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 hyperkitty should I use?

1.3.12 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 hyperkitty have?

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

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

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