How severe is CVE-2020-0618?

CVE-2020-0618 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2020-0618 being actively exploited?

Yes. CVE-2020-0618 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-09-18, which means active exploitation has been confirmed. It should be prioritised for remediation.

What products are affected by CVE-2020-0618?

CVE-2020-0618 primarily affects Microsoft Sql Server. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2020-0618?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.

Does CVE-2020-0618 have an EU (EUVD) identifier?

Yes. CVE-2020-0618 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2020-2113. It is also flagged as exploited in the EUVD (since 2024-09-18).

When was CVE-2020-0618 published?

CVE-2020-0618 was published on 2020-02-11 and last updated on 2026-06-17.

CVE-2020-0618

CVE-2020-0618 is a high-severity vulnerability in Microsoft Sql Server with a CVSS 3.x base score of 8.8. It is listed in CISA's Known Exploited Vulnerabilities (KEV) catalog, confirming it has been exploited in the wild (added 2024-09-18). The underlying weakness is classified as CWE-502.

Key facts

Severity: High (CVSS 3.x base score 8.8)
CVSS v2: 6.5
EPSS exploit prediction: 99% (100th percentile)
Actively exploited: Yes — listed in CISA KEV (added 2024-09-18)
EU (EUVD) id: EUVD-2020-2113
EU exploitation: Flagged exploited in the ENISA EU Vulnerability Database (since 2024-09-18)
Weakness: CWE-502
Affected product: Microsoft Sql Server
Published: 2020-02-11
Last modified: 2026-06-17

Description

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

Frequently asked questions

What is CVE-2020-0618?: 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'.
How severe is CVE-2020-0618?: CVE-2020-0618 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2020-0618 being actively exploited?: Yes. CVE-2020-0618 is on CISA's Known Exploited Vulnerabilities (KEV) catalog, added on 2024-09-18, which means active exploitation has been confirmed. It should be prioritised for remediation.
What products are affected by CVE-2020-0618?: CVE-2020-0618 primarily affects Microsoft Sql Server. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2020-0618?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Because this CVE is known to be actively exploited, treat remediation as urgent — CISA KEV typically sets a short remediation deadline.
Does CVE-2020-0618 have an EU (EUVD) identifier?: Yes. CVE-2020-0618 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2020-2113. It is also flagged as exploited in the EUVD (since 2024-09-18).
When was CVE-2020-0618 published?: CVE-2020-0618 was published on 2020-02-11 and last updated on 2026-06-17.

References

Affected products (3)

cpe:2.3:a:microsoft:sql_server:2012:sp4:*:*:*:*:*:*
cpe:2.3:a:microsoft:sql_server:2014:sp3:*:*:*:*:*:*
cpe:2.3:a:microsoft:sql_server:2016:sp2:*:*:*:*:x64:*

More vulnerabilities in Microsoft Sql Server

CVE-2002-1145 — Critical (CVSS 10.0): The xp_runwebtask stored procedure in the Web Tasks component of Microsoft SQL Server 7.0 and 2000, Microsoft Data…
CVE-2002-0721 — Critical (CVSS 10.0): Microsoft SQL Server 7.0 and 2000 installs with weak permissions for extended stored procedures that are associated…
CVE-2018-8273 — Critical (CVSS 9.8): A buffer overflow vulnerability exists in the Microsoft SQL Server that could allow remote code execution on an…
CVE-2009-3126 — Critical (CVSS 9.3): Integer overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Office XP SP3, Office 2003 SP3,…
CVE-2009-2528 — Critical (CVSS 9.3): GDI+ in Microsoft Office XP SP3 does not properly handle malformed objects in Office Art Property Tables, which allows…
CVE-2009-2504 — Critical (CVSS 9.3): Multiple integer overflows in unspecified APIs in GDI+ in Microsoft .NET Framework 1.1 SP1, .NET Framework 2.0 SP1 and…

All CVEs affecting Microsoft Sql Server →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.
CVE-2026-20131 — Critical (CVSS 10.0): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could…
CVE-2026-25632 — Critical (CVSS 10.0): EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water…
CVE-2025-14931 — Critical (CVSS 10.0): Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability.…

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →