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'.
CVE-2020-0618
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2024-09-18), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 8.8 retained for reference. Confidence: HIGH.
- Actively exploited in the wild (CISA-KEV)
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- 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 computedSeverity90% × 45%Exploitation100% × 40%Automatability0% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 99%
- EPSS %ILE
- 100%
- KEV
- ⚠ Exploited
Published
February 11, 2020
Last Modified
August 15, 2026
Advisory Details (4)
Auto-updated Jun 2, 2026Known 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-0618Security 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-0618Weakness Classification(2)
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 89× in last 7d / 361× 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,290 total refreshes for this CVE.
- 2026-09-19 19:13 UTCVendor advisory
- 2026-09-19 19:13 UTCGHSA enrichment
- 2026-09-19 15:05 UTCVendor advisory
- 2026-09-19 15:05 UTCGHSA enrichment
- 2026-09-19 10:55 UTCVendor advisory
- 2026-09-19 10:55 UTCGHSA enrichment
- 2026-09-19 06:48 UTCVendor advisory
- 2026-09-19 06:48 UTCGHSA enrichment
- 2026-09-19 02:35 UTCVendor advisory
- 2026-09-19 02:35 UTCGHSA enrichment
- 2026-09-18 22:28 UTCVendor advisory
- 2026-09-18 22:28 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 18:21 UTCVendor advisory
- 2026-09-18 18:21 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 14:14 UTCVendor advisory
- 2026-09-18 14:14 UTCGHSA enrichment
- 2026-09-18 10:07 UTCVendor advisory
- 2026-09-18 10:07 UTCGHSA enrichment
- 2026-09-18 06:00 UTCVendor advisory
- 2026-09-18 06:00 UTCGHSA enrichment
- 2026-09-18 01:53 UTCVendor advisory
- 2026-09-18 01:53 UTCGHSA enrichment
- 2026-09-17 21:46 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-17 21:46 UTCGHSA enrichment
- 2026-09-17 17:38 UTCVendor advisory
- 2026-09-17 17:38 UTCGHSA enrichment
- 2026-09-17 13:30 UTCVendor advisory
- 2026-09-17 13:30 UTCGHSA enrichment
- 2026-09-17 09:23 UTCVendor advisory
- 2026-09-17 09:23 UTCGHSA enrichment
- 2026-09-17 05:15 UTCVendor advisory
- 2026-09-17 05:15 UTCGHSA enrichment
- 2026-09-17 01:08 UTCVendor advisory
- 2026-09-17 01:08 UTCGHSA enrichment
- 2026-09-16 21:01 UTCVendor advisory
- 2026-09-16 21:01 UTCGHSA enrichment
- 2026-09-16 16:53 UTCEG score recompute
- 2026-09-16 16:53 UTCVendor advisory
- 2026-09-16 16:53 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 14:04 UTCEPSS rescore
- 2026-09-16 14:04 UTCEPSS rescore
- 2026-09-16 12:46 UTCVendor advisory
- 2026-09-16 12:46 UTCGHSA enrichment
- 2026-09-16 08:39 UTCVendor advisory
- 2026-09-16 08:38 UTCGHSA enrichment
- 2026-09-16 04:29 UTCVendor advisory
- 2026-09-16 04:29 UTCGHSA enrichment
- 2026-09-16 00:21 UTCVendor advisory
- 2026-09-16 00:21 UTCGHSA enrichment
- 2026-09-15 20:12 UTCVendor advisory
- 2026-09-15 20:12 UTCGHSA enrichment
- 2026-09-15 16:04 UTCVendor advisory
- 2026-09-15 16:04 UTCGHSA enrichment
- 2026-09-15 11:57 UTCVendor advisory
- 2026-09-15 11:56 UTCGHSA enrichment
- 2026-09-15 07:49 UTCVendor advisory
- 2026-09-15 07:49 UTCGHSA enrichment
- 2026-09-15 03:41 UTCVendor advisory
- 2026-09-15 03:41 UTCGHSA enrichment
- 2026-09-14 23:34 UTCVendor advisory
- 2026-09-14 23:34 UTCGHSA enrichment
- 2026-09-14 19:26 UTCVendor advisory
- 2026-09-14 19:26 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 15:19 UTCVendor advisory
- 2026-09-14 15:19 UTCGHSA enrichment
- 2026-09-14 11:11 UTCVendor advisory
- 2026-09-14 11:11 UTCGHSA enrichment
- 2026-09-14 07:04 UTCVendor advisory
- 2026-09-14 07:04 UTCGHSA enrichment
- 2026-09-14 02:57 UTCVendor advisory
- 2026-09-14 02:57 UTCGHSA enrichment
- 2026-09-13 22:49 UTCVendor advisory
- 2026-09-13 22:49 UTCGHSA enrichment
- 2026-09-13 18:42 UTCVendor advisory
- 2026-09-13 18:42 UTCGHSA enrichment
- 2026-09-13 14:35 UTCVendor advisory
- 2026-09-13 14:35 UTCGHSA enrichment
- 2026-09-13 10:28 UTCVendor advisory
- 2026-09-13 10:28 UTCGHSA enrichment
- 2026-09-13 06:20 UTCVendor advisory
- 2026-09-13 06:20 UTCGHSA enrichment
- 2026-09-13 02:13 UTCVendor advisory
- 2026-09-13 02:13 UTCGHSA enrichment
- 2026-09-12 22:05 UTCVendor advisory
- 2026-09-12 22:05 UTCGHSA enrichment
- 2026-09-12 17:57 UTCVendor advisory
- 2026-09-12 17:57 UTCGHSA enrichment
- 2026-09-12 13:50 UTCVendor advisory
- 2026-09-12 13:50 UTCGHSA enrichment
- 2026-09-12 09:43 UTCVendor advisory
- 2026-09-12 09:43 UTCGHSA enrichment
- 2026-09-12 05:36 UTCVendor advisory
- 2026-09-12 05:36 UTCGHSA enrichment
- 2026-09-12 01:29 UTCVendor advisory
- 2026-09-12 01:29 UTCGHSA enrichment
- 2026-09-11 21:22 UTCVendor advisory
Publicly available exploits
(6 references)Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCitstarsec/CVE-2020-0618First seen May 13, 2022
Melissa
Open source ↗ - Exploit-DBEDB-48816First seen Sep 17, 2020
Microsoft SQL Server Reporting Services 2016 - Remote Code Execution
Open source ↗ - GitHub PoCwortell/cve-2020-0618First seen Feb 18, 2020
CVE-2020-0618 Honeypot
Open source ↗ - GitHub PoCeuphrat1ca/CVE-2020-0618First seen Feb 15, 2020
SQL Server Reporting Services(CVE-2020-0618)中的RCE
Open source ↗ - Metasploitexploit/windows/http/ssrs_navcorrector_viewstate✓ verifiedFirst seen Feb 11, 2020
SQL Server Reporting Services (SSRS) ViewState Deserialization
Open source ↗ - Nucleihttp/cves/2020/CVE-2020-0618.yamlFirst seen Jan 1, 2020
Microsoft SQL Server Reporting Services - Remote Code Execution
Open source ↗
Frequently asked(6)
What is CVE-2020-0618?
When was CVE-2020-0618 disclosed?
Is CVE-2020-0618 actively exploited?
What is the CVSS score of CVE-2020-0618?
Which products are affected by CVE-2020-0618?
How do I remediate CVE-2020-0618?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2020-0618
Is Your Infrastructure Affected by CVE-2020-0618?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.