CVE-2020-0601 Microsoft Windows CryptoAPI Spoofing Vulnerability
Microsoft Windows CryptoAPI (Crypt32.dll) contains a spoofing vulnerability in the way it 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. A successful exploit could also allow the attacker to conduct man-in-the-middle attacks and decrypt confidential information on user connections to the affected software. The vulnerability is also known under the moniker of CurveBall.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 3 Nov 2021.
- Rated High severity (CVSS 8.1, scored by CISA).
- It has been in the catalogue for 1,829 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
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'.
Affected Versions
| Product | Versions |
|---|---|
| Microsoft Windows | 10 Version 1803 for 32-bit Systems 10 Version 1803 for x64-based Systems 10 Version 1803 for ARM64-based Systems 10 Version 1809 for 32-bit Systems 10 Version 1809 for x64-based Systems 10 Version 1809 for ARM64-based Systems |
| Microsoft Windows Server | version 1803 (Core Installation) 2019 2019 (Core installation) 2016 2016 (Core installation) |
| Microsoft Windows 10 Version 1903 for 32-bit Systems | unspecified |
| Microsoft Windows 10 Version 1903 for x64-based Systems | unspecified |
| Microsoft Windows 10 Version 1903 for ARM64-based Systems | unspecified |
| Microsoft Windows Server, version 1903 (Server Core installation) | unspecified |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
- 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2020-0601 and every other exploited flaw on the list.
Sources
- CISA Known Exploited Vulnerabilities catalogue
- NVD: CVE-2020-0601
- CVE record: CVE-2020-0601
- FIRST EPSS
- portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601
- packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept
- packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept
