Windows Graphics Component Remote Code Execution Vulnerability
CVE-2023-21823
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-02-14), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.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
- 7.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
- 92.0%
- KEV
- ⚠ Exploited
Published
February 14, 2023
Last Modified
October 30, 2025
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-21823Security 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-21823Weakness 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 75× in last 7d / 385× 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 741 total refreshes for this CVE.
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:18 UTCEG score recompute
- 2026-07-23 00:14 UTCEG score recompute
- 2026-07-23 00:14 UTCVendor advisory
- 2026-07-23 00:14 UTCGHSA enrichment
- 2026-07-22 23:06 UTCEG score recompute
- 2026-07-22 20:10 UTCGHSA enrichment
- 2026-07-22 19:40 UTCCISA KEV update
- 2026-07-22 16:07 UTCEG score recompute
- 2026-07-22 16:07 UTCVendor advisory
- 2026-07-22 16:07 UTCGHSA enrichment
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 12:01 UTCVendor advisory
- 2026-07-22 12:01 UTCGHSA enrichment
- 2026-07-22 07:57 UTCVendor advisory
- 2026-07-22 07:57 UTCGHSA enrichment
- 2026-07-22 03:54 UTCVendor advisory
- 2026-07-22 03:54 UTCGHSA enrichment
- 2026-07-21 23:45 UTCVendor advisory
- 2026-07-21 23:44 UTCGHSA enrichment
- 2026-07-21 19:14 UTCEG score recompute
- 2026-07-21 19:14 UTCVendor advisory
- 2026-07-21 19:14 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:10 UTCVendor advisory
- 2026-07-21 15:09 UTCGHSA enrichment
- 2026-07-21 14:37 UTCCISA KEV update
- 2026-07-21 11:06 UTCVendor advisory
- 2026-07-21 11:06 UTCGHSA enrichment
- 2026-07-21 07:02 UTCVendor advisory
- 2026-07-21 07:02 UTCGHSA enrichment
- 2026-07-21 02:59 UTCVendor advisory
- 2026-07-21 02:59 UTCGHSA enrichment
- 2026-07-20 22:55 UTCVendor advisory
- 2026-07-20 22:55 UTCGHSA enrichment
- 2026-07-20 18:52 UTCEG score recompute
- 2026-07-20 18:52 UTCVendor advisory
- 2026-07-20 18:52 UTCGHSA enrichment
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-20 14:49 UTCGHSA enrichment
- 2026-07-20 10:46 UTCGHSA enrichment
- 2026-07-20 06:43 UTCVendor advisory
- 2026-07-20 06:42 UTCGHSA enrichment
- 2026-07-20 02:18 UTCVendor advisory
- 2026-07-20 02:18 UTCGHSA enrichment
- 2026-07-19 22:14 UTCVendor advisory
- 2026-07-19 22:14 UTCGHSA enrichment
- 2026-07-19 18:11 UTCEG score recompute
- 2026-07-19 18:11 UTCVendor advisory
- 2026-07-19 18:11 UTCGHSA enrichment
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 14:07 UTCVendor advisory
- 2026-07-19 14:07 UTCGHSA enrichment
- 2026-07-19 10:03 UTCVendor advisory
- 2026-07-19 10:03 UTCGHSA enrichment
- 2026-07-19 06:00 UTCEG score recompute
- 2026-07-19 06:00 UTCVendor advisory
- 2026-07-19 06:00 UTCGHSA enrichment
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 01:57 UTCGHSA enrichment
- 2026-07-18 21:52 UTCVendor advisory
- 2026-07-18 21:52 UTCGHSA enrichment
- 2026-07-18 17:49 UTCVendor advisory
- 2026-07-18 17:49 UTCGHSA enrichment
- 2026-07-18 13:46 UTCEG score recompute
- 2026-07-18 13:46 UTCVendor advisory
- 2026-07-18 13:46 UTCGHSA enrichment
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 09:43 UTCVendor advisory
- 2026-07-18 09:43 UTCGHSA enrichment
- 2026-07-18 05:40 UTCVendor advisory
- 2026-07-18 05:40 UTCGHSA enrichment
- 2026-07-18 01:37 UTCVendor advisory
- 2026-07-18 01:37 UTCGHSA enrichment
- 2026-07-17 21:34 UTCVendor advisory
- 2026-07-17 21:34 UTCGHSA enrichment
- 2026-07-17 17:31 UTCVendor advisory
- 2026-07-17 17:31 UTCGHSA enrichment
- 2026-07-17 13:27 UTCVendor advisory
- 2026-07-17 13:27 UTCGHSA enrichment
- 2026-07-17 09:24 UTCEG score recompute
- 2026-07-17 09:24 UTCVendor advisory
- 2026-07-17 09:24 UTCGHSA enrichment
- 2026-07-17 05:20 UTCVendor advisory
- 2026-07-17 05:20 UTCGHSA enrichment
- 2026-07-17 01:16 UTCVendor advisory
- 2026-07-17 01:16 UTCGHSA enrichment
- 2026-07-16 21:13 UTCVendor advisory
- 2026-07-16 21:13 UTCGHSA enrichment
- 2026-07-16 17:10 UTCVendor advisory
- 2026-07-16 17:09 UTCGHSA enrichment
- 2026-07-16 17:04 UTCCISA KEV update
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-16 17:01 UTCEPSS rescore
- 2026-07-16 13:05 UTCGHSA enrichment
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCElizarfish/CVE-2023-21823First seen Apr 20, 2023
CVE-2023-21823 PoC
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
- CVE-2006-10003EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS 94%HIGH
- CVE-2013-7381EG 9.8CRITICAL
- CVE-2014-0048EG 9.8EPSS 93%CRITICAL
- CVE-2007-4559EG 9.8EPSS 98%CRITICAL
- CVE-2013-3900NVD 5.5EG 9.0 KEVEPSS 99%MEDIUM
- CVE-2013-2094NVD 8.4EG 9.0 KEVEPSS 99%HIGH
- CVE-2014-9356EG 8.6EPSS 91%HIGH
- CVE-2014-5282EG 8.1HIGH
- CVE-2014-8141EG 7.8EPSS 94%HIGH
Same CWE
10 shownCWE-190
- CVE-2009-0947EG 9.8CRITICAL
- CVE-2013-2729EG 9.8 KEVEPSS 99%CRITICAL
- CVE-2005-1141EG 9.8CRITICAL
- CVE-2005-0102EG 9.8CRITICAL
- CVE-2002-0391EG 9.8EPSS 99%CRITICAL
- CVE-2002-0639EG 9.8EPSS 97%CRITICAL
- CVE-2013-3486EG 9.6CRITICAL
- CVE-2013-2596NVD 7.8EG 9.0 KEVHIGH
- CVE-2012-5054NVD 8.8EG 9.0 KEVEPSS 97%HIGH
- CVE-2011-1823NVD 7.8EG 9.0 KEVEPSS 99%HIGH
Frequently asked(6)
What is CVE-2023-21823?
When was CVE-2023-21823 disclosed?
Is CVE-2023-21823 actively exploited?
What is the CVSS score of CVE-2023-21823?
Which products are affected by CVE-2023-21823?
How do I remediate CVE-2023-21823?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-21823
Is Your Infrastructure Affected by CVE-2023-21823?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.