Vulnerability Database · PyPI · keep · Version
keep 1.4.1
1.4.1 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 1 High 0 Medium 0 Low 0 Unrated 0
-
Released 23 Feb 2017
Licence MIT
Also known from other sources 1
Newer releases 25
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
keep 1.4.1 vulnerabilities
1 vulnerability cover keep 1.4.1. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2022-30877: Code Execution Backdoor in keep | 9.8 critical | No fix published | 08 Jun 2022 |
Looking for another version, or everything Vulert holds for keep?
Questions
About keep 1.4.1
Is keep 1.4.1 vulnerable?
Yes. 1 vulnerability in the Vulert database cover keep 1.4.1: 1 critical, 0 high, 0 medium and 0 low. Each entry above names the fixed version to move to.
Is 1.4.1 the latest release of keep?
No. 1.4.1 was published 23 Feb 2017, 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 keep for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the keep version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.