How severe is CVE-2020-0601?

CVE-2020-0601 has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2020-0601?

Affected package information for CVE-2020-0601 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2020-0601?

No fixed version has been published for CVE-2020-0601 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2020-0601 actively exploited in the wild?

Yes. There are 30 known exploit references for CVE-2020-0601, including 2 documented proof-of-concept exploits on Exploit-DB and 17 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2020-0601?

CVE-2020-0601 has an EPSS (Exploit Prediction Scoring System) score of 94.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2020-0601 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2020-0601 (Microsoft Windows CryptoAPI Spoofing Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2021-11-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-05-03. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2020-0601 published, and has it been updated?

CVE-2020-0601 was published on January 14, 2020 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2021-11-03 — agencies required to remediate by 2022-05-03

CVE-2020-0601

HIGH

Also known asBIT-golang-2020-0601GO-2022-0535

Published

Jan 14, 2020

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

30 known

EPSS Exploitation Probability

via FIRST.org ↗

94.1%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source, aka 'Windows CryptoAPI Spoofing Vulnerability'.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-47933localwindows

Microsoft Windows - CryptoAPI (Crypt32.dll) Elliptic Curve Cryptography (ECC) Spoof Code-Signing Certificate

by Oliver Lyak · Jan 15, 2020

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2020-0601 in your stack?

O3 detects CVE-2020-0601 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works