CVE-2026-24291
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 · uneditedIncorrect permission assignment for critical resource in Windows Accessibility Infrastructure (ATBroker.exe) 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 confidenceWindows Accessibility Infrastructure (ATBroker.exe) contains incorrect permission assignments on critical resources, allowing a local authorized attacker to escalate privileges by exploiting improper access controls on the accessibility broker component.
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
- 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.
-
Check Windows versionOpen Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the installed Windows version and build number.Affected if The build number falls below any of these thresholds: 14393.8957 (Win10 1607), 17763.8511 (Win10 1809), 19044.7058 (Win10 21h2/22h2), 22631.6783 (Win11 23h2), 26100.7979 (Win11 24h2/25h2), or 28000.1719 (Win11 26h1).
-
Locate ATBroker.exeSearch for ATBroker.exe using 'where /r C:\Windows ATBroker.exe' or 'Get-ChildItem -Path C:\Windows -Recurse -Filter ATBroker.exe -ErrorAction SilentlyContinue' in PowerShell.Affected if ATBroker.exe exists on the system in the Windows directory.
-
Verify accessibility features are enabledCheck if accessibility features are active by reviewing registry keys under 'HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Accessibility' or checking if the ATBroker service is running via 'sc query ATBroker' or 'Get-Service ATBroker' in PowerShell.Affected if ATBroker service is present and running, or accessibility components are registered in the system.
-
Examine file permissions on ATBroker.exeRight-click ATBroker.exe, go to Properties > Security tab, or run 'icacls C:\Windows\System32\ATBroker.exe' in Command Prompt to view the access control list.Affected if Any non-administrator or non-system account has Write, Modify, or Full Control permissions on ATBroker.exe beyond the expected Read/Execute permissions.
A system is affected if it runs a Windows version with a build number below the thresholds listed AND ATBroker.exe exists with overly permissive access controls allowing unauthorized write or execute access.
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
Review and correct file system permissions on ATBroker.exe and related accessibility infrastructure components to enforce least-privilege access controls, ensuring only appropriate system accounts have write or execute permissions.
Windows Security Update (KB) for respective build version - install the latest cumulative update for your Windows version from Microsoft Update Catalog
- Check current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Identify the specific build number from the affected versions list for your Windows edition
- Apply the latest Windows Security Update from Windows Update or Microsoft Update Catalog
- For enterprise environments, deploy the update via WSUS or Group Policy
- After update installation, verify the build number matches or exceeds the fixed version: Windows 10 1607 should be 10.0.14393.8957 or later; Windows 10 1809 should be 10.0.17763.8511 or later; Windows 10 21h2 should be 10.0.19044.7058 or later; Windows 10 22h2 should be 10.0.19045.7058 or later; Windows 11 23h2 should be 10.0.22631.6783 or later; Windows 11 24h2 should be 10.0.26100.7979 or later;
- Restart the system to complete the update installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24291 — 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-24291 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