CVE-2019-0604

CRITICALNVD 9.89.8—
EchelonGraph scoreHIGH confidence

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

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

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package, aka 'Microsoft SharePoint Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0594.

CVSS v3
9.8
EG Score
9.8CRITICALhigh confidence
EG Risk
99
EG Risk 99/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
Severity98% × 45%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low mission impact; Act at medium or high.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
100%
EPSS %ILE
99th
KEV
⚠ Exploited

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that sooner than your standard update timelines at low mission impact and as soon as possible at medium or high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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

March 5, 2019

Last Modified

October 29, 2025

Advisory Details (3)

Auto-updated Oct 1, 2026
⚠️ Active exploitation confirmed. Fix referenced — no release confirmed yet. Sources: cisa, microsoft.
cisa🔴 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-2019-0604
microsoftMentions a patch (unverified)

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-2019-0604
generic🔴 Active Exploitation

CVE-2019-0604 - PSIRT.COM

http://www.securityfocus.com/bid/106914

Vendor Advisories for CVE-2019-0604(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 92× in last 7d / 398× 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,631 total refreshes for this CVE.

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

Publicly available exploits

(6 references)

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

  • GitHub PoCGh0st0ne/weaponized-0604
    First seen Apr 22, 2021

    Automated tool to exploit sharepoint CVE-2019-0604

    Open source ↗
  • Exploit-DBEDB-48053
    First seen Jan 21, 2020

    Microsoft SharePoint - Deserialization Remote Code Execution

    Open source ↗
  • GitHub PoCboxhg/CVE-2019-0604
    First seen Dec 10, 2019

    详解 k8gege的SharePoint RCE exploit cve-2019-0604-exp.py的代码，动手制作自己的payload

    Open source ↗
  • GitHub PoCm5050/CVE-2019-0604
    First seen Sep 15, 2019

    CVE-2019-0604: SharePoint RCE detection rules and sample PCAP

    Open source ↗
  • GitHub PoCk8gege/CVE-2019-0604
    First seen Jun 26, 2019

    cve-2019-0604 SharePoint RCE exploit

    Open source ↗
  • GitHub PoClinhlhq/CVE-2019-0604
    First seen Mar 23, 2019

    CVE-2019-0604

    Open source ↗

Related CVEs(same CWE)

Frequently asked(6)

What is CVE-2019-0604?
CVE-2019-0604 is a critical vulnerability published on March 5, 2019. A remote code execution vulnerability exists in Microsoft SharePoint when the software fails to check the source markup of an application package, aka 'Microsoft SharePoint Remote Code Execution Vulnerability'. This CVE ID is unique from CVE-2019-0594.
When was CVE-2019-0604 disclosed?
CVE-2019-0604 was first published on March 5, 2019, with the most recent update on October 29, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-0604 actively exploited?
Yes. CISA added CVE-2019-0604 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft SharePoint. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2019-0604?
CVE-2019-0604 has a CVSS v3 base score of 9.8 (NVD).
Which products are affected by CVE-2019-0604?
CVE-2019-0604 affects Microsoft SharePoint.
How do I remediate CVE-2019-0604?
A fix for CVE-2019-0604 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2019-0604 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-0604

Explore →

Is Your Infrastructure Affected by CVE-2019-0604?

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

Book a Demo →Browse All CVEs