Vulnerability Database · PyPI · hyperkitty · Version
hyperkitty 1.0.0rc1
1.0.0rc1 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.3.12.
Critical 0 High 1 Medium 0 Low 0 Unrated 1
-
Released 18 Apr 2015
Licence GPL-3.0
Also known from other sources 2
Newer releases 41
Database updated 23/Oct/2026
Release and licence data published by PyPI. 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 Vulnerabilities affecting this version
hyperkitty 1.0.0rc1 vulnerabilities
2 vulnerabilities cover hyperkitty 1.0.0rc1. Open the full list 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 |
Looking for another version, or everything Vulert holds for hyperkitty?
Questions
About hyperkitty 1.0.0rc1
Is hyperkitty 1.0.0rc1 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover hyperkitty 1.0.0rc1: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 1.3.12, and each entry above names the fixed version to move to.
Which version of hyperkitty should I use instead of 1.0.0rc1?
1.3.12 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.0.0rc1 the latest release of hyperkitty?
No. 1.0.0rc1 was published 18 Apr 2015, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
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.