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

Q: How do I fix CVE-2022-30885?

pyesasky: upgrade to newer than 1.4.2. Exact commands for each OS are on this page.

Q: Is CVE-2022-30885 being exploited?

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

Q: What does CVE-2022-30885 affect?

CVE-2022-30885 affects pyesasky. Severity is critical (CVSS 9.8). The pyesasky 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.0-1.4.2.

Q: How urgent is CVE-2022-30885?

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

This week

CRITICAL 9.8REMOTEUPGRADE

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

The pyesasky 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.0-1.4.2.

Why this priority

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

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): MITRE · Vendor: esa

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

Am I affected?

Timeline

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

esa pyesasky UPGRADE

Affected: >= 1.2.0 and <= 1.4.2

Fixed in: newer than 1.4.2

Safe to downgrade to: a release before 1.2.0

1. Check installed version

pip show pyesasky

2. UPGRADE to newer than 1.4.2

pip install --upgrade "pyesasky>1.4.2"

3. If no update is available yet, DOWNGRADE to a release before 1.2.0

pip index versions pyesasky pip install "pyesasky<1.2.0"

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-30885?

pyesasky: upgrade to newer than 1.4.2. Exact commands for each OS are on this page.

Is CVE-2022-30885 being exploited?

CVE-2022-30885 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-30885 affect?

CVE-2022-30885 affects pyesasky. Severity is critical (CVSS 9.8). The pyesasky 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.0-1.4.2.

How urgent is CVE-2022-30885?

Priority 65/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