CVE-2021-43572: The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1

Q: How do I fix CVE-2021-43572?

ecdsa-python: upgrade to 2.0.1. Exact commands for each OS are on this page.

Q: Is CVE-2021-43572 being exploited?

CVE-2021-43572 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-2021-43572 affect?

CVE-2021-43572 affects ecdsa-python. Severity is critical (CVSS 9.8). The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.

Q: How urgent is CVE-2021-43572?

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

This week

CRITICAL 9.8REMOTEUPGRADE

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

The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.

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	1.2% (top 31%)
CISA exploited list	No
Weakness	CWE-347
Published	2021-11-09
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: starkbank

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

Am I affected?

Timeline

2021-11-09 22:15 UTCPublished CVE record published
2026-06-17 04:11 UTCUpdated Record last modified

starkbank ecdsa-python UPGRADE

Affected: < 2.0.1

Fixed in: 2.0.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ecdsa-python || rpm -q ecdsa-python || ecdsa-python --version

2. UPGRADE to 2.0.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ecdsa-python

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ecdsa-python

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2021-43572?

ecdsa-python: upgrade to 2.0.1. Exact commands for each OS are on this page.

Is CVE-2021-43572 being exploited?

CVE-2021-43572 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-2021-43572 affect?

CVE-2021-43572 affects ecdsa-python. Severity is critical (CVSS 9.8). The verify function in the Stark Bank Python ECDSA library (aka starkbank-escada or ecdsa-python) before 2.0.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.

How urgent is CVE-2021-43572?

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

Software pages

Python vulnerabilities

References

← Back to latest CVEs