CVE-2020-0601

CRITICALNVD 8.19.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2021-11-03), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.1 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 89%CVSS: 8.1Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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'.

CVSS v3
8.1
EG Score
9.0(high)
EG Risk
81(Attend)
EG Risk 81/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
89%
EPSS %ILE
100%
KEV
⚠ Exploited

Published

January 14, 2020

Last Modified

December 18, 2025

Advisory Details (4)

Auto-updated Jun 3, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2020-0601
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0601
generic

Packet Storm

http://packetstormsecurity.com/files/155961/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html
generic

Packet Storm

http://packetstormsecurity.com/files/155960/CurveBall-Microsoft-Windows-CryptoAPI-Spoofing-Proof-Of-Concept.html

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
stdlib—1.13.7—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 91× in last 7d / 374× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 1,327 total refreshes for this CVE.

  1. 2026-09-19 16:08 UTCVendor advisory
  2. 2026-09-19 16:08 UTCGHSA enrichment
  3. 2026-09-19 11:59 UTCVendor advisory
  4. 2026-09-19 11:59 UTCGHSA enrichment
  5. 2026-09-19 07:52 UTCVendor advisory
  6. 2026-09-19 07:52 UTCGHSA enrichment
  7. 2026-09-19 03:45 UTCVendor advisory
  8. 2026-09-19 03:45 UTCGHSA enrichment
  9. 2026-09-18 23:38 UTCVendor advisory
  10. 2026-09-18 23:38 UTCGHSA enrichment
  11. 2026-09-18 19:31 UTCEG score recompute
  12. 2026-09-18 19:31 UTCVendor advisory
  13. 2026-09-18 19:31 UTCGHSA enrichment
  14. 2026-09-18 19:23 UTCEPSS rescore
  15. 2026-09-18 19:20 UTCCISA KEV update
  16. 2026-09-18 15:24 UTCVendor advisory
  17. 2026-09-18 15:24 UTCGHSA enrichment
  18. 2026-09-18 14:15 UTCCISA KEV update
  19. 2026-09-18 11:17 UTCVendor advisory
  20. 2026-09-18 11:17 UTCGHSA enrichment
  21. 2026-09-18 07:10 UTCVendor advisory
  22. 2026-09-18 07:10 UTCGHSA enrichment
  23. 2026-09-18 03:03 UTCVendor advisory
  24. 2026-09-18 03:03 UTCGHSA enrichment
  25. 2026-09-17 22:55 UTCVendor advisory
Show 75 more
  1. 2026-09-17 22:55 UTCGHSA enrichment
  2. 2026-09-17 18:47 UTCVendor advisory
  3. 2026-09-17 18:46 UTCGHSA enrichment
  4. 2026-09-17 14:38 UTCVendor advisory
  5. 2026-09-17 14:38 UTCGHSA enrichment
  6. 2026-09-17 10:30 UTCVendor advisory
  7. 2026-09-17 10:30 UTCGHSA enrichment
  8. 2026-09-17 06:22 UTCVendor advisory
  9. 2026-09-17 06:22 UTCGHSA enrichment
  10. 2026-09-17 02:12 UTCVendor advisory
  11. 2026-09-17 02:12 UTCGHSA enrichment
  12. 2026-09-16 22:04 UTCVendor advisory
  13. 2026-09-16 22:04 UTCGHSA enrichment
  14. 2026-09-16 17:57 UTCEG score recompute
  15. 2026-09-16 17:57 UTCVendor advisory
  16. 2026-09-16 17:57 UTCGHSA enrichment
  17. 2026-09-16 14:10 UTCCISA KEV update
  18. 2026-09-16 14:04 UTCEPSS rescore
  19. 2026-09-16 14:04 UTCEPSS rescore
  20. 2026-09-16 13:49 UTCVendor advisory
  21. 2026-09-16 13:49 UTCGHSA enrichment
  22. 2026-09-16 09:42 UTCVendor advisory
  23. 2026-09-16 09:41 UTCGHSA enrichment
  24. 2026-09-16 05:34 UTCVendor advisory
  25. 2026-09-16 05:34 UTCGHSA enrichment
  26. 2026-09-16 01:27 UTCVendor advisory
  27. 2026-09-16 01:27 UTCGHSA enrichment
  28. 2026-09-15 21:20 UTCVendor advisory
  29. 2026-09-15 21:20 UTCGHSA enrichment
  30. 2026-09-15 17:13 UTCVendor advisory
  31. 2026-09-15 17:13 UTCGHSA enrichment
  32. 2026-09-15 13:06 UTCVendor advisory
  33. 2026-09-15 13:06 UTCGHSA enrichment
  34. 2026-09-15 08:59 UTCVendor advisory
  35. 2026-09-15 08:59 UTCGHSA enrichment
  36. 2026-09-15 04:52 UTCVendor advisory
  37. 2026-09-15 04:51 UTCGHSA enrichment
  38. 2026-09-15 00:43 UTCVendor advisory
  39. 2026-09-15 00:43 UTCGHSA enrichment
  40. 2026-09-14 20:36 UTCVendor advisory
  41. 2026-09-14 20:36 UTCGHSA enrichment
  42. 2026-09-14 19:24 UTCCISA KEV update
  43. 2026-09-14 16:29 UTCVendor advisory
  44. 2026-09-14 16:29 UTCGHSA enrichment
  45. 2026-09-14 12:22 UTCVendor advisory
  46. 2026-09-14 12:22 UTCGHSA enrichment
  47. 2026-09-14 08:15 UTCVendor advisory
  48. 2026-09-14 08:15 UTCGHSA enrichment
  49. 2026-09-14 04:08 UTCVendor advisory
  50. 2026-09-14 04:08 UTCGHSA enrichment
  51. 2026-09-14 00:01 UTCVendor advisory
  52. 2026-09-14 00:01 UTCGHSA enrichment
  53. 2026-09-13 19:54 UTCVendor advisory
  54. 2026-09-13 19:54 UTCGHSA enrichment
  55. 2026-09-13 15:47 UTCVendor advisory
  56. 2026-09-13 15:47 UTCGHSA enrichment
  57. 2026-09-13 11:39 UTCVendor advisory
  58. 2026-09-13 11:39 UTCGHSA enrichment
  59. 2026-09-13 07:31 UTCVendor advisory
  60. 2026-09-13 07:31 UTCGHSA enrichment
  61. 2026-09-13 03:23 UTCVendor advisory
  62. 2026-09-13 03:23 UTCGHSA enrichment
  63. 2026-09-12 23:15 UTCVendor advisory
  64. 2026-09-12 23:15 UTCGHSA enrichment
  65. 2026-09-12 19:08 UTCVendor advisory
  66. 2026-09-12 19:07 UTCGHSA enrichment
  67. 2026-09-12 15:00 UTCEG score recompute
  68. 2026-09-12 15:00 UTCVendor advisory
  69. 2026-09-12 15:00 UTCGHSA enrichment
  70. 2026-09-12 14:56 UTCEPSS rescore
  71. 2026-09-12 10:53 UTCVendor advisory
  72. 2026-09-12 10:52 UTCGHSA enrichment
  73. 2026-09-12 06:43 UTCVendor advisory
  74. 2026-09-12 06:42 UTCGHSA enrichment
  75. 2026-09-12 02:34 UTCVendor advisory

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCeastmountyxz/CVE-2020-0601-EXP
    First seen Feb 17, 2020

    这资源是作者复现微软签字证书漏洞CVE-2020-0601，结合相关资源及文章实现。推荐大家结合作者博客，理解ECC算法、Windows验证机制，并尝试自己复现可执行文件签名证书和HTTPS劫持的例子。作为网络安全初学者，自己确实很菜，但希望坚持下去，加油！

    Open source ↗
  • GitHub PoCioncodes/Curveball
    First seen Jan 28, 2020

    PoC for CVE-2020-0601 - CryptoAPI exploit

    Open source ↗
  • GitHub PoCgentilkiwi/curveball
    First seen Jan 20, 2020

    CVE-2020-0601 #curveball - Alternative Key Calculator

    Open source ↗
  • GitHub PoCIIICTECH/-CVE-2020-0601-ECC---EXPLOIT
    First seen Jan 19, 2020

    CurveBall (CVE-2020-0601) - PoC CVE-2020-0601, or commonly referred to as CurveBall, is a vulnerability in which the signature of certificates using elliptic curve cryptography (ECC) is not correctly verified. Attackers can supply hand-rolled generators, bypassing validation, antivirus & all non-protections.

    Open source ↗
  • GitHub PoCRrUZi/Awesome-CVE-2020-0601
    First seen Jan 16, 2020

    😂An awesome curated list of repos for CVE-2020-0601.

    Open source ↗
  • GitHub PoCsaleemrashid/badecparams
    First seen Jan 16, 2020

    Proof of Concept for CVE-2020-0601

    Open source ↗
  • Exploit-DBEDB-47933
    First seen Jan 15, 2020

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

    Open source ↗
  • GitHub PoC0xxon/cve-2020-0601
    First seen Jan 15, 2020

    Zeek package to detect CVE-2020-0601

    Open source ↗
  • GitHub PoC0xxon/cve-2020-0601-plugin
    First seen Jan 15, 2020

    Zeek package that uses OpenSSL to detect CVE-2020-0601 exploit attempts

    Open source ↗
  • GitHub PoCkudelskisecurity/chainoffools
    First seen Jan 15, 2020

    A PoC for CVE-2020-0601

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(6)

What is CVE-2020-0601?
CVE-2020-0601 is a critical vulnerability published on January 14, 2020. 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,…
When was CVE-2020-0601 disclosed?
CVE-2020-0601 was first published in the National Vulnerability Database on January 14, 2020, with the most recent update on December 18, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-0601 actively exploited?
Yes. CISA added CVE-2020-0601 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2020-0601?
CVE-2020-0601 has a CVSS v3 base score of 8.1 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2020-0601?
CVE-2020-0601 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2020-0601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-0601, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-0601

Explore →

Is Your Infrastructure Affected by CVE-2020-0601?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs