CVE-2026-48565
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 · uneditedUntrusted search path in Windows Narrator Braille allows an authorized attacker to elevate privileges locally.
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 local privilege escalation vulnerability in Windows Narrator's Braille component. The untrusted search path flaw allows an authorized attacker to place a malicious DLL or executable in a location where Narrator searches for files, causing it to load the attacker's code with elevated privileges when the service or application runs.
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 dataall versionsCVSS 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.
-
Verify Narrator Braille component is enabledOpen Windows Settings > Accessibility > Narrator, or run 'narrator.exe' from command line, and confirm the Braille display option is turned on in Narrator settingsAffected if Narrator with Braille support is enabled and running
-
Identify Narrator executable locationOpen Task Manager, find Narrator process, right-click and select 'Open file location' to locate the narratorservice.exe or related executableAffected if Narrator process is running on the system
-
Check write permissions on Narrator program directoriesRight-click the Narrator program folder identified in step 2, select Properties > Security, and verify which users/groups have Write or Modify permissions to that directoryAffected if Any standard user account has Write or Modify access to Narrator program directories
-
Enumerate DLL search path for NarratorUse Process Monitor (procmon.exe) from Sysinternals: filter by Process Name = narratorservice.exe, filter Operation = Load Image, and capture a trace while starting Narrator to see which DLL paths are searchedAffected if Narrator loads DLLs from user-writable directories in its search path
-
Scan Narrator directories for unexpected DLLsUse File Explorer to list all .dll files in the Narrator program folder and subfolders; compare against expected Microsoft DLLs, or run 'dir /s /b C:\Windows\System32\narrator*.dll' to find Narrator-related DLLsAffected if Unexpected or suspicious DLL files are present in Narrator program folders
If Narrator Braille support is enabled and any user has Write access to directories in Narrator's DLL search path, the system is vulnerable to DLL hijacking attacks via this CVE.
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.
From vendor dataApply vendor security patches from Microsoft for this vulnerability. If a patch is unavailable, restrict write permissions on directories in Narrator's search path and ensure only trusted executables can be loaded.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-48565 — 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-48565 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