Actively exploitedKnown ransomware use

CVE-2020-0618 Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability

Microsoft SQL Server Reporting Services contains a deserialization vulnerability when handling page requests incorrectly. An authenticated attacker can exploit this vulnerability to execute code in the context of the Report Server service account.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch nowCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 18 Sep 2024.
  • CISA lists it as known to be used in ransomware campaigns.
  • Rated Critical severity (CVSS 9.8, scored by CISA).
  • It has been in the catalogue for 779 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

A remote code execution vulnerability exists in Microsoft SQL Server Reporting Services when it incorrectly handles page requests, aka 'Microsoft SQL Server Reporting Services Remote Code Execution Vulnerability'.

Affected Versions

ProductVersions
Microsoft Microsoft SQL Server2012 for 32-bit Systems Service Pack 4 (QFE)
2012 for x64-based Systems Service Pack 4 (QFE)
2016 for x64-based Systems Service Pack 2 (CU)
Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (GDR)unspecified
Microsoft Microsoft SQL Server 2014 Service Pack 3 for x64-based Systems (CU)unspecified
Microsoft Microsoft SQL Server 2016 for x64-based Systems Service Pack 2 (GDR)unspecified
Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (GDR)unspecified
Microsoft Microsoft SQL Server 2014 Service Pack 3 for 32-bit Systems (CU)unspecified

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft SQL Server. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 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. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2020-0618 and every other exploited flaw on the list.

Check My Exposure