CVE-2026-25186
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 · uneditedExposure of sensitive information to an unauthorized actor in Windows Accessibility Infrastructure (ATBroker.exe) allows an authorized attacker to disclose information 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 information disclosure vulnerability in Windows Accessibility Infrastructure (ATBroker.exe). An authorized local attacker can exploit this to access sensitive information due to improper access controls within the accessibility broker service.
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.14393.8957< 10.0.17763.8511< 10.0.19044.7058< 10.0.19045.7058< 10.0.22631.6783< 10.0.26100.7979< 10.0.26200.7979< 10.0.28000.1719CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Check Windows version and build numberOpen Command Prompt or PowerShell and run: winver or systeminfo | findstr /C:"OS Name" /C:"OS Version"Affected if The displayed version and build number fall within the affected ranges: Windows 10 1607 < 10.0.14393.8957, Windows 10 1809 < 10.0.17763.8511, Windows 10 21h2 < 10.0.19044.7058, Windows 10 22h2 < 10.0.19045.7058, Windows 11 23h2 < 10.0.22631.6783, Windows 11 24h2 < 10.0.26100.7979, Windows 11 25h2 <
-
Verify ATBroker.exe exists on the systemCheck for the presence of ATBroker.exe in the system. Run: dir C:\Windows\System32\ATBroker.exe or Get-Item C:\Windows\System32\ATBroker.exeAffected if ATBroker.exe is present on the system (this is the component with the access control vulnerability)
-
Confirm the system has accessibility features enabledCheck if any accessibility features or assistive technology applications are installed or running. Look in Control Panel > Ease of Access > Ease of Access Center, or check running processes for assistive technology services.Affected if Accessibility features or assistive technology applications are enabled or installed on the system, as ATBroker.exe manages these components
-
Verify local user account exposureReview local user accounts on the system by running: net user or Get-LocalUser. Identify if untrusted or low-privilege local accounts exist.Affected if The system has multiple local user accounts where untrusted or low-privilege users could potentially exploit the accessibility broker service
A system is likely affected if it runs a Windows version within the affected build ranges AND has ATBroker.exe present with accessibility features enabled, allowing local untrusted users to potentially access sensitive information through improper access controls in the accessibility broker service.
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.14393.895710.0.17763.851110.0.19044.7058
Apply the relevant Microsoft security update for CVE-2026-25186. Restrict local user privileges where possible and verify that only necessary accounts have access to the system.
Windows 10 1607: build 10.0.14393.8957 or later | Windows 10 1809: build 10.0.17763.8511 or later | Windows 10 21h2: build 10.0.19044.7058 or later | Windows 10 22h2: build 10.0.19045.7058 or later | Windows 11 23h2: build 10.0.22631.6783 or later | Windows 11 24h2: build 10.0.26100.7979 or later |
- 1. Identify the current Windows version and build number by running 'winver' or 'systeminfo' in Command Prompt
- 2. Determine which Windows 10 or 11 version/build is installed from the list of affected versions
- 3. Apply Windows updates via Settings > Update & Security > Windows Update, or use WSUS/SCCM for enterprise deployments
- 4. Alternatively, download and install the specific cumulative update for your Windows version from Microsoft Update Catalog
- 5. Verify the update was installed successfully and the build number matches or exceeds the fixed version for your Windows release
- 6. Restart the system if prompted to complete the installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25186 — 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-25186 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