Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

keep vulnerabilities and fixes

Recent CVEs affecting keep, with upgrade or downgrade steps. 1 tracked.

keep has 1 tracked vulnerability, 1 critical. A fixed release or vendor patch exists for 0. Most recent: 2022-06-08. Highest priority: CVE-2022-30877 (score 66/100).

FAQ

How do I fix keep vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is keep being exploited right now?

None of the tracked keep CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which keep CVE should I patch first?

CVE-2022-30877 currently ranks highest (66/100): The keep for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party.

← Back to latest CVEs