CVE-2020-1350

CRITICALNVD 10.010.0—
EchelonGraph scoreHIGH confidence

Score elevated to 10.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 10.0 retained for reference. Confidence: HIGH.

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

A fix is available — apply it.

A remote code execution vulnerability exists in Windows Domain Name System servers when they fail to properly handle requests, aka 'Windows DNS Server Remote Code Execution Vulnerability'.

CVSS v3
10.0
EG Score
10.0CRITICALhigh confidence
EG Risk
100
EG Risk 100/100CISA SSVC

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
Severity100% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.
EPSS PROB
97%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low mission impact; Act at medium or high.

A fix is available. Apply it sooner than your standard update timelines at low mission impact and as soon as possible at medium or high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 14, 2020

Last Modified

December 18, 2025

Advisory Details (3)

Auto-updated Oct 3, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa, microsoft.
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-1350
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-1350
generic

Packet Storm

http://packetstormsecurity.com/files/158484/SIGRed-Windows-DNS-Denial-Of-Service.html

Vendor Advisories for CVE-2020-1350(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 87× in last 7d / 389× 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,611 total refreshes for this CVE.

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

Publicly available exploits

(10 references)

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

  • GitHub PoCgraph-inc/CVE-2020-1350
    First seen Jul 18, 2020

    Scanner and Mitigator for CVE 2020-1350

    Open source ↗
  • GitHub PoCconnormcgarr/CVE-2020-1350
    First seen Jul 17, 2020

    CVE-2020-1350 Proof-of-Concept

    Open source ↗
  • GitHub PoCcaptainGeech42/CVE-2020-1350
    First seen Jul 16, 2020

    Denial of Service PoC for CVE-2020-1350 (SIGRed)

    Open source ↗
  • GitHub PoCcorelight/SIGRed
    First seen Jul 15, 2020

    Detection of attempts to exploit Microsoft Windows DNS server via CVE-2020-1350 (AKA SIGRed)

    Open source ↗
  • GitHub PoCmaxpl0it/CVE-2020-1350-DoS
    First seen Jul 15, 2020

    A denial-of-service proof-of-concept for CVE-2020-1350

    Open source ↗
  • GitHub PoCT13nn3s/CVE-2020-1350
    First seen Jul 15, 2020

    This Powershell Script is checking if your server is vulnerable for the CVE-2020-1350 Remote Code Execution flaw in the Windows DNS Service

    Open source ↗
  • GitHub PoCmr-r3b00t/CVE-2020-1350
    First seen Jul 14, 2020
    Open source ↗
  • GitHub PoCZephrFish/CVE-2020-1350_HoneyPoC
    First seen Jul 14, 2020

    HoneyPoC: Proof-of-Concept (PoC) script to exploit SIGRed (CVE-2020-1350). Achieves Domain Admin on Domain Controllers running Windows Server 2000 up to Windows Server 2019.

    Open source ↗
  • GitHub PoCzoomerxsec/Fake_CVE-2020-1350
    First seen Jul 14, 2020

    Fake exploit tool, designed to rickroll users attempting to actually exploit.

    Open source ↗
  • GitHub PoCpsc4re/NSE-scripts
    First seen Mar 11, 2020

    NSE scripts to detect CVE-2020-1350 SIGRED and CVE-2020-0796 SMBGHOST, CVE-2021-21972, proxyshell, CVE-2021-34473

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2020-1350?
CVE-2020-1350 is a critical vulnerability published on July 14, 2020. A remote code execution vulnerability exists in Windows Domain Name System servers when they fail to properly handle requests, aka 'Windows DNS Server Remote Code Execution Vulnerability'.
When was CVE-2020-1350 disclosed?
CVE-2020-1350 was first published on July 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-1350 actively exploited?
Yes. CISA added CVE-2020-1350 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 attention. A fix is available. Apply it.
What is the CVSS score of CVE-2020-1350?
CVE-2020-1350 has a CVSS v3 base score of 10.0 (NVD).
Which products are affected by CVE-2020-1350?
CVE-2020-1350 affects Microsoft Windows.
How do I remediate CVE-2020-1350?
A fix for CVE-2020-1350 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2020-1350 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-1350

Explore →

Is Your Infrastructure Affected by CVE-2020-1350?

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

Book a Demo →Browse All CVEs