CVE-2026-58635
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper neutralization of special elements used in a command ('command injection') in Windows Narrator Braille allows an authorized attacker to elevate privileges locally.
In the news
Third-party coverage- Microsoft July 2026 Patch Tuesday fixes massive 570 flaws, 3 zero-days
- Microsoft CVE Summary - Bleeping Computer
Surfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis is a command injection vulnerability in Windows Narrator's Braille functionality that allows a local authorized attacker to inject malicious commands and escalate privileges. The vulnerability stems from improper neutralization of special elements in the Narrator Braille component, enabling privilege elevation from a lower-privileged user context.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 10.0.17763.9020< 10.0.19044.7548< 10.0.19045.7548< 10.0.26100.8875< 10.0.26100.8875< 10.0.28000.2269< 10.0.28000.2525< 10.0.17763.9020< 10.0.20348.5386CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Windows version and build numberOpen Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows version and build numberAffected if The installed version falls within any of these ranges: Windows 10 1809 < 10.0.17763.9020, Windows 10 21h2 < 10.0.19044.7548, Windows 10 22h2 < 10.0.19045.7548, Windows 11 24h2 < 10.0.26100.8875, Windows 11 25h2 < 10.0.26100.8875, Windows 11 26h1 < 10.0.28000.2269 or < 10.0.28000.2525, Windows Serve
-
Verify Narrator service statusOpen Services console (services.msc) or run 'Get-Service Narrator' in PowerShell to check if the Narrator accessibility service is enabled or runningAffected if Narrator service is currently enabled or set to start automatically on the system
-
Confirm Braille display configurationCheck for installed Braille display devices or Braille support settings in Windows accessibility options. Look for Braille-related services or drivers in Device Manager or check accessibility settings via Control Panel > Ease of Access > NarratorAffected if Braille display support or Braille functionality is configured, enabled, or a Braille device is installed on the system
-
Inspect Narrator configuration filesCheck for Narrator configuration in user profile settings. Look in %LOCALAPPDATA%\Microsoft\Narrator or registry keys under HKCU\Software\Microsoft\Narrator for custom Braille settingsAffected if Non-default Narrator or Braille configurations exist that may indicate manual setup of the vulnerable component
A system is affected if it runs a Windows version within the specified vulnerable build ranges AND has Narrator with Braille functionality enabled or configured on the system.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped10.0.17763.902010.0.19044.754810.0.19045.7548
Apply Microsoft security patches for this vulnerability once released; in the interim, restrict user access to Narrator settings and monitor for suspicious processes related to the Braille accessibility feature.
Microsoft Security Update (specific build numbers per Windows version as listed above)
- Identify the current Windows version by running 'winver' or checking System Properties
- Determine the applicable Windows edition (Windows 10 1809, 21h2, 22h2, Windows 11 24h2/25h2/26h1, Windows Server 2019, or Windows Server 2022)
- Apply the appropriate security update for your Windows version: For Windows 10 1809/Windows Server 2019: install update building to 10.0.17763.9020 or later; For Windows 10 21h2: install update building to 10.0.19044.7548 or later; For Windows 10 22h2: install update building to 10.0.19045.7548 or later; For Windows 11 24h2/25h2: install update building to 10.0.26100.8875 or later; For Windows 11
- Restart the system after applying the update
- Verify the fix by checking the installed Windows version matches or exceeds the fixed build number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-58635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-58635 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data