dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-45604

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 10.0.22631.7219 / 10.0.26100.8655 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
Out-of-bounds read 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

An out-of-bounds read vulnerability exists in the Windows Application Identity (AppID) subsystem. The flaw allows a locally authorized attacker to read memory contents beyond intended boundaries, potentially exposing sensitive information such as credentials, session tokens, or other data resident in memory.

MitigationApply the Microsoft security update for CVE-2026-45604 through standard Windows Update or patch management channels. Restrict local administrative access to minimize the pool of authorized users who could exploit this vulnerability.

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 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
Windows Server 2025Operating system
Affected:< 10.0.26100.32995

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
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full Windows build number including the 10.0.xxxx.xxxx format
    Affected if The build number falls below the patched versions: 22631.7219 for 23h2, 26100.8655 for 24h2, 26200.8655 for 25h2, 28000.2269 for 26h1, or 26100.32995 for Server 2025
  2. Verify AppID service status
    Open Services console (services.msc) or run 'Get-Service AppID' in PowerShell to check if the Application Identity service is running
    Affected if The AppID service is enabled and running, as the vulnerability exists in this subsystem
  3. Confirm Windows edition
    Run 'winver' or check System Properties to confirm if the system is Windows 11 or Windows Server 2025 specifically, since the affected version ranges differ
    Affected if The system is Windows 11 version 23h2, 24h2, 25h2, 26h1, or Windows Server 2025 and the build is below the corresponding threshold

A system is affected if it runs Windows 11 23h2/24h2/25h2/26h1 or Windows Server 2025 with a build number below the patched thresholds AND has the AppID service enabled.

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.22631.7219 / 10.0.26100.8655 / 10.0.26100.32995 or later
Fixed in 10.0.22631.721910.0.26100.865510.0.26100.32995
Interim mitigation

Apply the Microsoft security update for CVE-2026-45604 through standard Windows Update or patch management channels. Restrict local administrative access to minimize the pool of authorized users who could exploit this vulnerability.

Recommended fix High confidence

Apply Windows security updates to reach the minimum fixed build for your Windows version (23h2: 10.0.22631.7219, 24h2: 10.0.26100.8655, 25h2: 10.0.26200.8655, 26h1: 10.0.28000.2269, Server 2025: 10.0.26100.32995)

  1. Open Settings > Windows Update and check for available updates
  2. Install all pending Windows updates until the build number reaches or exceeds the fixed version for your Windows edition
  3. For Windows 11 23h2: ensure build is 10.0.22631.7219 or later
  4. For Windows 11 24h2: ensure build is 10.0.26100.8655 or later
  5. For Windows 11 25h2: ensure build is 10.0.26200.8655 or later
  6. For Windows 11 26h1: ensure build is 10.0.28000.2269 or later
  7. For Windows Server 2025: ensure build is 10.0.26100.32995 or later
  8. Restart the system as prompted to complete the update installation

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

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45604 — 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-45604 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