Windows Search Remote Code Execution Vulnerability
CVE-2023-36884
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-07-17), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 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
- 7.5
- 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
July 11, 2023
Last Modified
August 10, 2026
Advisory Details (2)
Auto-updated Jun 4, 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-2023-36884Security Update Guide - Microsoft Security Response Center
Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update
https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36884Weakness Classification(1)
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 95× in last 7d / 400× 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,454 total refreshes for this CVE.
- 2026-09-20 20:26 UTCVendor advisory
- 2026-09-20 20:26 UTCGHSA enrichment
- 2026-09-20 16:42 UTCVendor advisory
- 2026-09-20 16:42 UTCGHSA enrichment
- 2026-09-20 12:57 UTCVendor advisory
- 2026-09-20 12:56 UTCGHSA enrichment
- 2026-09-20 09:09 UTCVendor advisory
- 2026-09-20 09:09 UTCGHSA enrichment
- 2026-09-20 05:24 UTCVendor advisory
- 2026-09-20 05:24 UTCGHSA enrichment
- 2026-09-20 01:40 UTCVendor advisory
- 2026-09-20 01:40 UTCGHSA enrichment
- 2026-09-19 21:56 UTCVendor advisory
- 2026-09-19 21:56 UTCGHSA enrichment
- 2026-09-19 18:11 UTCVendor advisory
- 2026-09-19 18:11 UTCGHSA enrichment
- 2026-09-19 14:27 UTCVendor advisory
- 2026-09-19 14:27 UTCGHSA enrichment
- 2026-09-19 10:43 UTCVendor advisory
- 2026-09-19 10:43 UTCGHSA enrichment
- 2026-09-19 06:59 UTCVendor advisory
- 2026-09-19 06:59 UTCGHSA enrichment
- 2026-09-19 03:15 UTCVendor advisory
- 2026-09-19 03:15 UTCGHSA enrichment
- 2026-09-18 23:31 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-18 23:31 UTCGHSA enrichment
- 2026-09-18 19:47 UTCEG score recompute
- 2026-09-18 19:47 UTCVendor advisory
- 2026-09-18 19:47 UTCGHSA enrichment
- 2026-09-18 19:20 UTCCISA KEV update
- 2026-09-18 16:03 UTCVendor advisory
- 2026-09-18 16:02 UTCGHSA enrichment
- 2026-09-18 14:15 UTCCISA KEV update
- 2026-09-18 12:15 UTCVendor advisory
- 2026-09-18 12:15 UTCGHSA enrichment
- 2026-09-18 08:31 UTCVendor advisory
- 2026-09-18 08:31 UTCGHSA enrichment
- 2026-09-18 04:47 UTCVendor advisory
- 2026-09-18 04:47 UTCGHSA enrichment
- 2026-09-18 01:03 UTCVendor advisory
- 2026-09-18 01:03 UTCGHSA enrichment
- 2026-09-17 21:19 UTCVendor advisory
- 2026-09-17 21:19 UTCGHSA enrichment
- 2026-09-17 17:35 UTCVendor advisory
- 2026-09-17 17:35 UTCGHSA enrichment
- 2026-09-17 13:51 UTCVendor advisory
- 2026-09-17 13:51 UTCGHSA enrichment
- 2026-09-17 10:06 UTCVendor advisory
- 2026-09-17 10:06 UTCGHSA enrichment
- 2026-09-17 06:21 UTCVendor advisory
- 2026-09-17 06:21 UTCGHSA enrichment
- 2026-09-17 02:35 UTCVendor advisory
- 2026-09-17 02:34 UTCGHSA enrichment
- 2026-09-16 22:50 UTCVendor advisory
- 2026-09-16 22:50 UTCGHSA enrichment
- 2026-09-16 19:05 UTCVendor advisory
- 2026-09-16 19:05 UTCGHSA enrichment
- 2026-09-16 15:21 UTCVendor advisory
- 2026-09-16 15:21 UTCGHSA enrichment
- 2026-09-16 14:10 UTCCISA KEV update
- 2026-09-16 11:37 UTCVendor advisory
- 2026-09-16 11:37 UTCGHSA enrichment
- 2026-09-16 07:52 UTCVendor advisory
- 2026-09-16 07:52 UTCGHSA enrichment
- 2026-09-16 04:05 UTCVendor advisory
- 2026-09-16 04:05 UTCGHSA enrichment
- 2026-09-16 00:21 UTCVendor advisory
- 2026-09-16 00:20 UTCGHSA enrichment
- 2026-09-15 20:36 UTCVendor advisory
- 2026-09-15 20:36 UTCGHSA enrichment
- 2026-09-15 16:43 UTCVendor advisory
- 2026-09-15 16:43 UTCGHSA enrichment
- 2026-09-15 12:59 UTCVendor advisory
- 2026-09-15 12:59 UTCGHSA enrichment
- 2026-09-15 09:15 UTCVendor advisory
- 2026-09-15 09:15 UTCGHSA enrichment
- 2026-09-15 05:31 UTCVendor advisory
- 2026-09-15 05:30 UTCGHSA enrichment
- 2026-09-15 01:44 UTCVendor advisory
- 2026-09-15 01:44 UTCGHSA enrichment
- 2026-09-14 22:00 UTCVendor advisory
- 2026-09-14 21:59 UTCGHSA enrichment
- 2026-09-14 19:24 UTCCISA KEV update
- 2026-09-14 18:14 UTCVendor advisory
- 2026-09-14 18:14 UTCGHSA enrichment
- 2026-09-14 14:29 UTCVendor advisory
- 2026-09-14 14:29 UTCGHSA enrichment
- 2026-09-14 10:45 UTCVendor advisory
- 2026-09-14 10:45 UTCGHSA enrichment
- 2026-09-14 07:01 UTCVendor advisory
- 2026-09-14 07:01 UTCGHSA enrichment
- 2026-09-14 03:17 UTCVendor advisory
- 2026-09-14 03:17 UTCGHSA enrichment
- 2026-09-13 23:33 UTCVendor advisory
- 2026-09-13 23:33 UTCGHSA enrichment
- 2026-09-13 19:49 UTCVendor advisory
- 2026-09-13 19:49 UTCGHSA enrichment
- 2026-09-13 16:05 UTCVendor advisory
- 2026-09-13 16:05 UTCGHSA enrichment
- 2026-09-13 12:21 UTCVendor advisory
Publicly available exploits
(5 references)Working exploit code is in the public domain (5 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCjakabakos/CVE-2023-36884-MS-Office-HTML-RCEFirst seen Sep 28, 2023
MS Office and Windows HTML RCE (CVE-2023-36884) - PoC and exploit
Open source ↗ - Open source ↗GitHub PoCridsoliveira/Fix-CVE-2023-36884First seen Jul 28, 2023
- GitHub PoCtarraschk/CVE-2023-36884-CheckerFirst seen Jul 17, 2023
Script to check for CVE-2023-36884 hardening
Open source ↗ - GitHub PoCzerosorai/CVE-2023-36884First seen Jul 15, 2023
This is an emergency solution while Microsoft addresses the vulnerability.
Open source ↗ - GitHub PoCMaxwitat/CVE-2023-36884-Scripts-for-Intune-Remediation-SCCM-Compliance-BaselineFirst seen Jul 12, 2023
The remediation script should set the reg entries described in https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36884 . The detection script checks if they exist. Provided AS-IS without any warrenty.
Open source ↗
Related CVEs(same CWE)
Frequently asked(6)
What is CVE-2023-36884?
When was CVE-2023-36884 disclosed?
Is CVE-2023-36884 actively exploited?
What is the CVSS score of CVE-2023-36884?
Which products are affected by CVE-2023-36884?
How do I remediate CVE-2023-36884?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-36884
Is Your Infrastructure Affected by CVE-2023-36884?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.