Improper neutralization of special elements used in a command ('command injection') in Windows Narrator Braille allows an authorized attacker to elevate privileges locally.
CVE-2026-58635
Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-14. the CNA's CVSS baseline 7.8; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.8
- EG Score
- 7.8(medium)
- EG Risk
- 51(Track)EG Risk 51/100SSVC: Track
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 computedSeverity78% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
July 14, 2026
Last Modified
August 28, 2026
Advisory Details (1)
Auto-updated Jul 14, 2026Security 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-2026-58635Vendor Advisories for CVE-2026-58635(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 31× in last 7d / 168× 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 245 total refreshes for this CVE.
- 2026-08-30 05:10 UTCEG score recompute
- 2026-08-30 05:10 UTCVendor advisory
- 2026-08-30 05:10 UTCGHSA enrichment
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-28 23:21 UTCEG score recompute
- 2026-08-28 23:21 UTCVendor advisory
- 2026-08-28 23:21 UTCGHSA enrichment
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 21:32 UTCEG score recompute
- 2026-08-27 21:32 UTCVendor advisory
- 2026-08-27 21:32 UTCGHSA enrichment
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 02:59 UTCEG score recompute
- 2026-08-27 02:59 UTCVendor advisory
- 2026-08-27 02:59 UTCGHSA enrichment
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 14:27 UTCVendor advisory
- 2026-08-26 14:27 UTCGHSA enrichment
- 2026-08-26 01:36 UTCEG score recompute
- 2026-08-26 01:36 UTCVendor advisory
- 2026-08-26 01:36 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:51 UTCVendor advisory
- 2026-08-25 09:51 UTCGHSA enrichment
- 2026-08-24 21:17 UTCEG score recompute
Show 75 moreShow fewer
- 2026-08-24 21:17 UTCVendor advisory
- 2026-08-24 21:17 UTCGHSA enrichment
- 2026-08-24 09:16 UTCVendor advisory
- 2026-08-24 09:16 UTCGHSA enrichment
- 2026-08-23 20:28 UTCVendor advisory
- 2026-08-23 20:28 UTCGHSA enrichment
- 2026-08-23 07:55 UTCEG score recompute
- 2026-08-23 07:55 UTCVendor advisory
- 2026-08-23 07:55 UTCGHSA enrichment
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 19:23 UTCVendor advisory
- 2026-08-22 19:23 UTCGHSA enrichment
- 2026-08-22 06:50 UTCEG score recompute
- 2026-08-22 06:50 UTCVendor advisory
- 2026-08-22 06:50 UTCGHSA enrichment
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 18:17 UTCGHSA enrichment
- 2026-08-21 05:44 UTCEG score recompute
- 2026-08-21 05:44 UTCVendor advisory
- 2026-08-21 05:44 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 17:11 UTCVendor advisory
- 2026-08-20 17:11 UTCGHSA enrichment
- 2026-08-20 05:43 UTCGHSA enrichment
- 2026-08-19 17:10 UTCEG score recompute
- 2026-08-19 17:10 UTCVendor advisory
- 2026-08-19 17:10 UTCGHSA enrichment
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:54 UTCVendor advisory
- 2026-08-19 15:54 UTCGHSA enrichment
- 2026-08-19 06:54 UTCVendor advisory
- 2026-08-19 06:54 UTCGHSA enrichment
- 2026-08-18 17:46 UTCVendor advisory
- 2026-08-18 17:46 UTCGHSA enrichment
- 2026-08-18 16:04 UTCEG score recompute
- 2026-08-18 16:04 UTCVendor advisory
- 2026-08-18 16:04 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-18 07:24 UTCGHSA enrichment
- 2026-08-17 18:51 UTCEG score recompute
- 2026-08-17 18:51 UTCVendor advisory
- 2026-08-17 18:51 UTCGHSA enrichment
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-17 09:46 UTCVendor advisory
- 2026-08-17 09:46 UTCGHSA enrichment
- 2026-08-16 21:14 UTCEG score recompute
- 2026-08-16 21:14 UTCVendor advisory
- 2026-08-16 21:14 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 08:41 UTCEG score recompute
- 2026-08-16 08:41 UTCVendor advisory
- 2026-08-16 08:41 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 20:08 UTCVendor advisory
- 2026-08-15 20:08 UTCGHSA enrichment
- 2026-08-15 07:35 UTCEG score recompute
- 2026-08-15 07:35 UTCVendor advisory
- 2026-08-15 07:35 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 17:42 UTCVendor advisory
- 2026-08-14 17:42 UTCGHSA enrichment
- 2026-08-14 17:18 UTCVendor advisory
- 2026-08-14 17:18 UTCGHSA enrichment
- 2026-08-14 09:45 UTCEG score recompute
- 2026-08-14 09:45 UTCVendor advisory
- 2026-08-14 09:45 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 21:12 UTCEG score recompute
- 2026-08-13 21:12 UTCVendor advisory
- 2026-08-13 21:12 UTCGHSA enrichment
- 2026-08-13 08:34 UTCVendor advisory
- 2026-08-13 08:34 UTCGHSA enrichment
- 2026-08-12 20:01 UTCEG score recompute
- 2026-08-12 20:01 UTCVendor advisory
- 2026-08-12 20:01 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 PoCDavidCarliez/CVE-2026-58635-PoCFirst seen Jul 15, 2026
Proof of concept for CVE-2026-58635
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
10 shownmsrc
Same CWE
10 shownCWE-77
- CVE-2015-7541EG 10.0CRITICAL
- CVE-2015-1815EG 10.0EPSS p97HIGH
- CVE-2014-1905EG 10.0EPSS p95HIGH
- CVE-2013-2810EG 10.0EPSS p93HIGH
- CVE-2014-5470EG 9.8EPSS p95CRITICAL
- CVE-2013-2513EG 9.8CRITICAL
- CVE-2015-20108EG 9.8CRITICAL
- CVE-2015-10096NVD 5.0EG 9.8CRITICAL
- CVE-2015-20107NVD 7.6EG 9.8EPSS p94CRITICAL
- CVE-2014-4982EG 9.8EPSS p91CRITICAL
Frequently asked(5)
What is CVE-2026-58635?
When was CVE-2026-58635 disclosed?
Is CVE-2026-58635 actively exploited?
What is the CVSS score of CVE-2026-58635?
How do I remediate CVE-2026-58635?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-58635
Is Your Infrastructure Affected by CVE-2026-58635?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.