Windows Common Log File System Driver Elevation of Privilege Vulnerability
CVE-2022-37969
Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-09-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 PROB
- 28%
- EPSS %ILE
- 98%
- KEV
- ⚠ Exploited
Published
September 13, 2022
Last Modified
January 13, 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-2022-37969Security 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-2022-37969Weakness 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 99× in last 7d / 424× 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,396 total refreshes for this CVE.
- 2026-09-08 11:03 UTCVendor advisory
- 2026-09-08 11:02 UTCGHSA enrichment
- 2026-09-08 07:12 UTCVendor advisory
- 2026-09-08 07:12 UTCGHSA enrichment
- 2026-09-08 03:23 UTCVendor advisory
- 2026-09-08 03:23 UTCGHSA enrichment
- 2026-09-07 23:35 UTCVendor advisory
- 2026-09-07 23:35 UTCGHSA enrichment
- 2026-09-07 19:46 UTCVendor advisory
- 2026-09-07 19:46 UTCGHSA enrichment
- 2026-09-07 15:58 UTCVendor advisory
- 2026-09-07 15:58 UTCGHSA enrichment
- 2026-09-07 12:09 UTCVendor advisory
- 2026-09-07 12:09 UTCGHSA enrichment
- 2026-09-07 08:20 UTCVendor advisory
- 2026-09-07 08:19 UTCGHSA enrichment
- 2026-09-07 04:29 UTCVendor advisory
- 2026-09-07 04:29 UTCGHSA enrichment
- 2026-09-07 00:38 UTCVendor advisory
- 2026-09-07 00:38 UTCGHSA enrichment
- 2026-09-06 20:49 UTCVendor advisory
- 2026-09-06 20:49 UTCGHSA enrichment
- 2026-09-06 17:00 UTCEG score recompute
- 2026-09-06 17:00 UTCVendor advisory
- 2026-09-06 17:00 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-06 13:11 UTCVendor advisory
- 2026-09-06 13:11 UTCGHSA enrichment
- 2026-09-06 09:22 UTCVendor advisory
- 2026-09-06 09:22 UTCGHSA enrichment
- 2026-09-06 05:33 UTCVendor advisory
- 2026-09-06 05:33 UTCGHSA enrichment
- 2026-09-06 01:44 UTCVendor advisory
- 2026-09-06 01:44 UTCGHSA enrichment
- 2026-09-05 21:56 UTCVendor advisory
- 2026-09-05 21:56 UTCGHSA enrichment
- 2026-09-05 18:07 UTCEG score recompute
- 2026-09-05 18:07 UTCVendor advisory
- 2026-09-05 18:06 UTCGHSA enrichment
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 14:17 UTCVendor advisory
- 2026-09-05 14:16 UTCGHSA enrichment
- 2026-09-05 10:27 UTCVendor advisory
- 2026-09-05 10:27 UTCGHSA enrichment
- 2026-09-05 06:38 UTCVendor advisory
- 2026-09-05 06:38 UTCGHSA enrichment
- 2026-09-05 02:47 UTCVendor advisory
- 2026-09-05 02:46 UTCGHSA enrichment
- 2026-09-04 22:57 UTCVendor advisory
- 2026-09-04 22:57 UTCGHSA enrichment
- 2026-09-04 19:08 UTCVendor advisory
- 2026-09-04 19:08 UTCGHSA enrichment
- 2026-09-04 17:38 UTCCISA KEV update
- 2026-09-04 15:19 UTCEG score recompute
- 2026-09-04 15:19 UTCVendor advisory
- 2026-09-04 15:19 UTCGHSA enrichment
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 11:31 UTCVendor advisory
- 2026-09-04 11:31 UTCGHSA enrichment
- 2026-09-04 07:42 UTCEG score recompute
- 2026-09-04 07:42 UTCVendor advisory
- 2026-09-04 07:42 UTCGHSA enrichment
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-04 03:53 UTCVendor advisory
- 2026-09-04 03:53 UTCGHSA enrichment
- 2026-09-04 00:03 UTCVendor advisory
- 2026-09-04 00:03 UTCGHSA enrichment
- 2026-09-03 20:14 UTCVendor advisory
- 2026-09-03 20:14 UTCGHSA enrichment
- 2026-09-03 16:25 UTCVendor advisory
- 2026-09-03 16:25 UTCGHSA enrichment
- 2026-09-03 12:36 UTCVendor advisory
- 2026-09-03 12:36 UTCGHSA enrichment
- 2026-09-03 08:47 UTCVendor advisory
- 2026-09-03 08:47 UTCGHSA enrichment
- 2026-09-03 04:58 UTCVendor advisory
- 2026-09-03 04:57 UTCGHSA enrichment
- 2026-09-03 01:07 UTCVendor advisory
- 2026-09-03 01:07 UTCGHSA enrichment
- 2026-09-02 21:18 UTCVendor advisory
- 2026-09-02 21:18 UTCGHSA enrichment
- 2026-09-02 17:33 UTCCISA KEV update
- 2026-09-02 17:29 UTCEG score recompute
- 2026-09-02 17:29 UTCVendor advisory
- 2026-09-02 17:28 UTCGHSA enrichment
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-02 13:38 UTCVendor advisory
- 2026-09-02 13:38 UTCGHSA enrichment
- 2026-09-02 09:48 UTCGHSA enrichment
- 2026-09-02 05:58 UTCVendor advisory
- 2026-09-02 05:58 UTCGHSA enrichment
- 2026-09-02 02:10 UTCVendor advisory
- 2026-09-02 02:09 UTCGHSA enrichment
- 2026-09-01 22:18 UTCVendor advisory
- 2026-09-01 22:18 UTCGHSA enrichment
- 2026-09-01 18:30 UTCVendor advisory
- 2026-09-01 18:30 UTCGHSA enrichment
- 2026-09-01 14:40 UTCVendor advisory
- 2026-09-01 14:40 UTCGHSA enrichment
- 2026-09-01 10:50 UTCVendor advisory
Publicly available exploits
(3 references)Working exploit code is in the public domain (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCEmilC3978/CVE-2022-37969PoCFirst seen Nov 25, 2025
Tutorial of CVE-2022-37969 with focus on the methodology of Kernel exploitation, not CVE's internal causes
Open source ↗ - Open source ↗GitHub PoCNoobCat2000/CVE-2022-37969First seen Jul 6, 2025
- GitHub PoCfortra/CVE-2022-37969First seen Mar 9, 2023
Windows LPE exploit for CVE-2022-37969
Open source ↗
Frequently asked(6)
What is CVE-2022-37969?
When was CVE-2022-37969 disclosed?
Is CVE-2022-37969 actively exploited?
What is the CVSS score of CVE-2022-37969?
Which products are affected by CVE-2022-37969?
How do I remediate CVE-2022-37969?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2022-37969
Is Your Infrastructure Affected by CVE-2022-37969?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.