Windows CNG Key Isolation Service Elevation of Privilege Vulnerability
CVE-2023-28229
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-10-04), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.0 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.0
- 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
- 2%
- EPSS %ILE
- 75%
- KEV
- ⚠ Exploited
Published
April 11, 2023
Last Modified
October 28, 2025
Advisory Details (2)
Auto-updated Jun 11, 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-28229Security 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-28229Weakness 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 103× in last 7d / 445× 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,473 total refreshes for this CVE.
- 2026-09-08 13:36 UTCVendor advisory
- 2026-09-08 13:36 UTCGHSA enrichment
- 2026-09-08 09:58 UTCVendor advisory
- 2026-09-08 09:57 UTCGHSA enrichment
- 2026-09-08 06:20 UTCVendor advisory
- 2026-09-08 06:20 UTCGHSA enrichment
- 2026-09-08 02:41 UTCVendor advisory
- 2026-09-08 02:41 UTCGHSA enrichment
- 2026-09-07 23:04 UTCVendor advisory
- 2026-09-07 23:04 UTCGHSA enrichment
- 2026-09-07 19:26 UTCEG score recompute
- 2026-09-07 19:26 UTCVendor advisory
- 2026-09-07 19:26 UTCGHSA enrichment
- 2026-09-07 15:59 UTCEPSS rescore
- 2026-09-07 15:48 UTCVendor advisory
- 2026-09-07 15:47 UTCGHSA enrichment
- 2026-09-07 12:10 UTCVendor advisory
- 2026-09-07 12:10 UTCGHSA enrichment
- 2026-09-07 08:32 UTCVendor advisory
- 2026-09-07 08:31 UTCGHSA enrichment
- 2026-09-07 04:52 UTCVendor advisory
- 2026-09-07 04:51 UTCGHSA enrichment
- 2026-09-07 01:13 UTCVendor advisory
- 2026-09-07 01:13 UTCGHSA enrichment
- 2026-09-06 21:34 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-06 21:34 UTCGHSA enrichment
- 2026-09-06 17:55 UTCVendor advisory
- 2026-09-06 17:55 UTCGHSA enrichment
- 2026-09-06 14:16 UTCEG score recompute
- 2026-09-06 14:16 UTCVendor advisory
- 2026-09-06 14:16 UTCGHSA enrichment
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 10:38 UTCVendor advisory
- 2026-09-06 10:38 UTCGHSA enrichment
- 2026-09-06 07:00 UTCGHSA enrichment
- 2026-09-06 03:22 UTCVendor advisory
- 2026-09-06 03:22 UTCGHSA enrichment
- 2026-09-05 23:44 UTCVendor advisory
- 2026-09-05 23:44 UTCGHSA enrichment
- 2026-09-05 20:04 UTCVendor advisory
- 2026-09-05 20:04 UTCGHSA enrichment
- 2026-09-05 16:26 UTCEG score recompute
- 2026-09-05 16:26 UTCVendor advisory
- 2026-09-05 16:26 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 12:48 UTCVendor advisory
- 2026-09-05 12:48 UTCGHSA enrichment
- 2026-09-05 09:10 UTCVendor advisory
- 2026-09-05 09:10 UTCGHSA enrichment
- 2026-09-05 05:32 UTCVendor advisory
- 2026-09-05 05:32 UTCGHSA enrichment
- 2026-09-05 01:54 UTCVendor advisory
- 2026-09-05 01:54 UTCGHSA enrichment
- 2026-09-04 22:16 UTCVendor advisory
- 2026-09-04 22:15 UTCGHSA enrichment
- 2026-09-04 18:36 UTCVendor advisory
- 2026-09-04 18:35 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 14:57 UTCEG score recompute
- 2026-09-04 14:57 UTCVendor advisory
- 2026-09-04 14:57 UTCGHSA enrichment
- 2026-09-04 13:58 UTCEPSS rescore
- 2026-09-04 11:19 UTCVendor advisory
- 2026-09-04 11:19 UTCGHSA enrichment
- 2026-09-04 07:41 UTCEG score recompute
- 2026-09-04 07:41 UTCVendor advisory
- 2026-09-04 07:40 UTCGHSA enrichment
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-04 03:59 UTCVendor advisory
- 2026-09-04 03:59 UTCGHSA enrichment
- 2026-09-04 00:18 UTCVendor advisory
- 2026-09-04 00:18 UTCGHSA enrichment
- 2026-09-03 20:39 UTCVendor advisory
- 2026-09-03 20:39 UTCGHSA enrichment
- 2026-09-03 17:02 UTCVendor advisory
- 2026-09-03 17:02 UTCGHSA enrichment
- 2026-09-03 13:22 UTCVendor advisory
- 2026-09-03 13:22 UTCGHSA enrichment
- 2026-09-03 09:44 UTCVendor advisory
- 2026-09-03 09:43 UTCGHSA enrichment
- 2026-09-03 06:06 UTCVendor advisory
- 2026-09-03 06:06 UTCGHSA enrichment
- 2026-09-03 02:28 UTCVendor advisory
- 2026-09-03 02:27 UTCGHSA enrichment
- 2026-09-02 22:49 UTCVendor advisory
- 2026-09-02 22:49 UTCGHSA enrichment
- 2026-09-02 19:08 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 15:27 UTCEG score recompute
- 2026-09-02 15:27 UTCVendor advisory
- 2026-09-02 15:27 UTCGHSA enrichment
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 11:47 UTCVendor advisory
- 2026-09-02 11:47 UTCGHSA enrichment
- 2026-09-02 08:09 UTCGHSA enrichment
- 2026-09-02 04:30 UTCVendor advisory
- 2026-09-02 04:29 UTCGHSA enrichment
- 2026-09-02 00:47 UTCVendor advisory
- 2026-09-02 00:47 UTCGHSA enrichment
- 2026-09-01 21:09 UTCVendor advisory
Publicly available exploits
(2 references)Working exploit code is in the public domain (2 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCbyt3n33dl3/CrackKeyIsoFirst seen Mar 27, 2024
it's a CVE-2023-28229 (Patched), but feel free to use it for check any outdated software or reseach
Open source ↗ - Open source ↗GitHub PoCY3A/CVE-2023-28229First seen Sep 4, 2023
Frequently asked(6)
What is CVE-2023-28229?
When was CVE-2023-28229 disclosed?
Is CVE-2023-28229 actively exploited?
What is the CVSS score of CVE-2023-28229?
Which products are affected by CVE-2023-28229?
How do I remediate CVE-2023-28229?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2023-28229
Is Your Infrastructure Affected by CVE-2023-28229?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.