dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-45594

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.14393.9234 / 10.0.17763.8880 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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 · unedited
Exposure of sensitive information to an unauthorized actor in Windows Application Identity (AppID) Subsystem 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 confidence

This is a local information disclosure vulnerability in the Windows Application Identity (AppID) Subsystem. An authorized attacker with local access can exploit this to disclose sensitive information that should be protected. The vulnerability resides in the AppID service component of Windows.

MitigationApply the relevant Microsoft security update for CVE-2026-45594 through Windows Update or Microsoft Update Catalog once released. Verify the patch is successfully installed on affected systems.

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
Windows 10 1607Operating system
Affected:< 10.0.14393.9234
Windows 10 1809Operating system
Affected:< 10.0.17763.8880
Windows 10 21h2Operating system
Affected:< 10.0.19044.7417
Windows 10 22h2Operating system
Affected:< 10.0.19045.7417
Windows 11 23h2Operating system
Affected:< 10.0.22631.7219
Windows 11 24h2Operating system
Affected:< 10.0.26100.8655
Windows 11 25h2Operating system
Affected:< 10.0.26200.8655
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Version"' or use PowerShell '[System.Environment]::OSVersion.Version' to obtain the build number
    Affected if The build number is lower than the threshold for your Windows version (see version ranges: 14393.9234, 17763.8880, 19044.7417, 19045.7417, 22631.7219, 26100.8655, 26200.8655, or 28000.2269)
  2. Confirm Windows version family
    Run 'winver' to identify whether you are on Windows 10 1607, 1809, 21h2, 22h2, or Windows 11 23h2, 24h2, 25h2, or 26h1
    Affected if The identified Windows version falls within the affected product list but your current build is below the version-specific threshold
  3. Verify AppID service presence
    Open Services (services.msc) or run 'Get-Service AppID' in PowerShell to locate the Application Identity service
    Affected if The AppID service exists on the system (this is a default Windows service)
  4. Check AppID service status
    Run 'Get-Service AppID' in PowerShell or check via services.msc to see if the service is running
    Affected if The AppID service is currently running on the system

You are affected if your Windows build version is lower than the threshold for your specific Windows version family AND the AppID service is present and running on your system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.14393.9234 / 10.0.17763.8880 / 10.0.19044.7417 or later
Fixed in 10.0.14393.923410.0.17763.888010.0.19044.7417
Interim mitigation

Apply the relevant Microsoft security update for CVE-2026-45594 through Windows Update or Microsoft Update Catalog once released. Verify the patch is successfully installed on affected systems.

Recommended fix High confidence

Install the latest Windows security updates from Microsoft Update (the fixed builds are: 10.0.14393.9234, 10.0.17763.8880, 10.0.19044.7417, 10.0.19045.7417, 10.0.22631.7219, 10.0.26100.8655, 10.0.26200.8655, 10.0.28000.2269 or later)

  1. Open Windows Settings and navigate to Windows Update
  2. Click 'Check for updates' to download and install the latest security updates
  3. Alternatively, manually install the specific KB update for your Windows version from the Microsoft Update Catalog
  4. Restart the system after installing updates
  5. Verify the Windows build version matches or exceeds the fixed version for your release (e.g., for Windows 10 22h2, verify build >= 10.0.19045.7417)
Caveat Standard Windows updateapply risks - ensure backups of critical data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45594 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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