CVE-2022-30877: The keep for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-30877 is a critical-severity flaw (CVSS 9.8) affecting keep. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The keep for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.2.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	2.6% (top 15%)
CISA exploited list	No
Published	2022-06-08
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: keep project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-06-08 18:15 UTCPublished CVE record published
2026-06-17 04:44 UTCUpdated Record last modified

keep project keep DOWNGRADE

Affected: 1.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy keep || rpm -q keep || keep --version

2. No fixed release: DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison keep sudo apt install keep=<VERSION_BEFORE_1.2> sudo apt-mark hold keep

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list keep sudo dnf downgrade keep-<VERSION_BEFORE_1.2> sudo dnf versionlock add keep

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-30877?

keep: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-30877 being exploited?

CVE-2022-30877 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-30877 affect?

CVE-2022-30877 affects keep. Severity is critical (CVSS 9.8). The keep for python, as distributed on PyPI, included a code-execution backdoor inserted by a third party. The current version, without this backdoor, is 1.2.

How urgent is CVE-2022-30877?

Priority 66/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities · PyPI packages vulnerabilities

References

← Back to latest CVEs