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 / 395× 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,300 total refreshes for this CVE.
- 2026-09-08 16:31 UTCVendor advisory
- 2026-09-08 16:31 UTCGHSA enrichment
- 2026-09-08 12:40 UTCVendor advisory
- 2026-09-08 12:40 UTCGHSA enrichment
- 2026-09-08 08:55 UTCGHSA enrichment
- 2026-09-08 05:11 UTCVendor advisory
- 2026-09-08 05:10 UTCGHSA enrichment
- 2026-09-08 01:25 UTCVendor advisory
- 2026-09-08 01:25 UTCGHSA enrichment
- 2026-09-07 21:41 UTCVendor advisory
- 2026-09-07 21:41 UTCGHSA enrichment
- 2026-09-07 17:57 UTCVendor advisory
- 2026-09-07 17:57 UTCGHSA enrichment
- 2026-09-07 14:13 UTCVendor advisory
- 2026-09-07 14:13 UTCGHSA enrichment
- 2026-09-07 10:25 UTCVendor advisory
- 2026-09-07 10:25 UTCGHSA enrichment
- 2026-09-07 06:40 UTCVendor advisory
- 2026-09-07 06:40 UTCGHSA enrichment
- 2026-09-07 02:55 UTCVendor advisory
- 2026-09-07 02:55 UTCGHSA enrichment
- 2026-09-06 23:08 UTCVendor advisory
- 2026-09-06 23:07 UTCGHSA enrichment
- 2026-09-06 19:22 UTCVendor advisory
- 2026-09-06 19:22 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-06 15:36 UTCEG score recompute
- 2026-09-06 15:36 UTCVendor advisory
- 2026-09-06 15:36 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 11:51 UTCVendor advisory
- 2026-09-06 11:51 UTCGHSA enrichment
- 2026-09-06 08:07 UTCVendor advisory
- 2026-09-06 08:07 UTCGHSA enrichment
- 2026-09-06 04:22 UTCVendor advisory
- 2026-09-06 04:22 UTCGHSA enrichment
- 2026-09-06 00:38 UTCVendor advisory
- 2026-09-06 00:38 UTCGHSA enrichment
- 2026-09-05 20:53 UTCVendor advisory
- 2026-09-05 20:53 UTCGHSA enrichment
- 2026-09-05 17:10 UTCEG score recompute
- 2026-09-05 17:10 UTCVendor advisory
- 2026-09-05 17:10 UTCGHSA enrichment
- 2026-09-05 15:26 UTCEPSS rescore
- 2026-09-05 13:23 UTCVendor advisory
- 2026-09-05 13:23 UTCGHSA enrichment
- 2026-09-05 09:39 UTCVendor advisory
- 2026-09-05 09:39 UTCGHSA enrichment
- 2026-09-05 05:55 UTCVendor advisory
- 2026-09-05 05:55 UTCGHSA enrichment
- 2026-09-05 02:11 UTCVendor advisory
- 2026-09-05 02:11 UTCGHSA enrichment
- 2026-09-04 22:27 UTCVendor advisory
- 2026-09-04 22:26 UTCGHSA enrichment
- 2026-09-04 18:39 UTCVendor advisory
- 2026-09-04 18:38 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 14:54 UTCVendor advisory
- 2026-09-04 14:54 UTCGHSA enrichment
- 2026-09-04 11:10 UTCVendor advisory
- 2026-09-04 11:10 UTCGHSA enrichment
- 2026-09-04 07:26 UTCVendor advisory
- 2026-09-04 07:26 UTCGHSA enrichment
- 2026-09-04 03:41 UTCVendor advisory
- 2026-09-04 03:41 UTCGHSA enrichment
- 2026-09-03 23:56 UTCVendor advisory
- 2026-09-03 23:56 UTCGHSA enrichment
- 2026-09-03 20:11 UTCVendor advisory
- 2026-09-03 20:11 UTCGHSA enrichment
- 2026-09-03 16:24 UTCVendor advisory
- 2026-09-03 16:24 UTCGHSA enrichment
- 2026-09-03 12:40 UTCVendor advisory
- 2026-09-03 12:40 UTCGHSA enrichment
- 2026-09-03 08:56 UTCVendor advisory
- 2026-09-03 08:56 UTCGHSA enrichment
- 2026-09-03 05:11 UTCVendor advisory
- 2026-09-03 05:10 UTCGHSA enrichment
- 2026-09-03 01:23 UTCVendor advisory
- 2026-09-03 01:23 UTCGHSA enrichment
- 2026-09-02 21:40 UTCVendor advisory
- 2026-09-02 21:39 UTCGHSA enrichment
- 2026-09-02 17:54 UTCVendor advisory
- 2026-09-02 17:53 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 14:07 UTCVendor advisory
- 2026-09-02 14:07 UTCGHSA enrichment
- 2026-09-02 10:19 UTCVendor advisory
- 2026-09-02 10:19 UTCGHSA enrichment
- 2026-09-02 06:35 UTCVendor advisory
- 2026-09-02 06:35 UTCGHSA enrichment
- 2026-09-02 02:52 UTCVendor advisory
- 2026-09-02 02:52 UTCGHSA enrichment
- 2026-09-01 23:07 UTCVendor advisory
- 2026-09-01 23:07 UTCGHSA enrichment
- 2026-09-01 19:22 UTCVendor advisory
- 2026-09-01 19:22 UTCGHSA enrichment
- 2026-09-01 15:35 UTCEG score recompute
- 2026-09-01 15:35 UTCVendor advisory
- 2026-09-01 15:35 UTCGHSA enrichment
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-09-01 11:49 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 ↗
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.