Windows AppX Deployment Service Elevation of Privilege Vulnerability
- Exploited
- No known exploitation
- Fix
- Fixed in Windows 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711 · Windows Server 10.0.20348.5870
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: Windows 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711 · Windows Server 10.0.20348.5870.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 9/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Windows AppX Deployment Service contains a flaw in its authorization checks that lets a user who already has low-privilege access on the local machine gain higher privileges. No user interaction is needed, and the bug gives the attacker elevated control over the system.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Incorrect authorization in Windows AppX Deployment Service allows an authorized attacker to elevate privileges locally.
cve.now Index
- Exploitation0/40No signal
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: Windows 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711 · Windows Server 10.0.20348.5870.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-116714 (Windows AppX Deployment Service Elevation of Privilege Vulnerability), using the cve.now data below. Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only. What cve.now has for CVE-2026-116714 (entry last updated 2026-11-10): Affected: - Microsoft Windows 10 Version 21H2: from 10.0.19044.0, fixed in 10.0.19044.7846 - Microsoft Windows 10 Version 22H2: from 10.0.19045.0, fixed in 10.0.19045.7846 - Microsoft Windows 11 version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7711 - Microsoft Windows 11 Version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7711 - Microsoft Windows Server 2022: from 10.0.20348.0, fixed in 10.0.20348.5870 Fixed versions: 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711, 10.0.20348.5870. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-116714 is not listed as of cve.now's last read. This KEV status is for CVE-2026-116714 only. If you also check another CVE, look up its own KEV status; never assume it from this one. How to check: - Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory. Verify against the linked advisories before concluding, and cite the date you read each one: - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-116714 Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing. Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action. Entry: https://cve.now/CVE-2026-116714 For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-116714.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
- First seen by cve.now
Affected versions
- Microsoft Windows 10 Version 21H2
From 10.0.19044.0 · fixed in 10.0.19044.7846
- Microsoft Windows 10 Version 22H2
From 10.0.19045.0 · fixed in 10.0.19045.7846
- Microsoft Windows 11 version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.7711
- Microsoft Windows 11 Version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.7711
- Microsoft Windows Server 2022
From 10.0.20348.0 · fixed in 10.0.20348.5870
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Patch
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-116714
Is CVE-2026-116714 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-116714?
Windows 10 Version 21H2: from 10.0.19044.0 before 10.0.19044.7846. Windows 10 Version 22H2: from 10.0.19045.0 before 10.0.19045.7846. Windows 11 version 23H2: from 10.0.22631.0 before 10.0.22631.7711. Windows 11 Version 23H2: from 10.0.22631.0 before 10.0.22631.7711. Windows Server 2022: from 10.0.20348.0 before 10.0.20348.5870.Source: cve.now feed data
How do I fix CVE-2026-116714?
Upgrade to a fixed version: Windows 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711 · Windows Server 10.0.20348.5870.Source: cve.now feed data