CVE-2026-32080
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 · uneditedUse after free in Windows WalletService 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 confidenceA use-after-free vulnerability exists in Windows WalletService where memory is accessed after being freed, allowing a locally authorized attacker to manipulate memory and elevate privileges to higher levels.
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.9060< 10.0.17763.8644< 10.0.20348.5020< 10.0.25398.2274< 10.0.26100.32690CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 Server version and build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows Server build numberAffected if The build number falls below 14393.9060 (Server 2016), 17763.8644 (Server 2019), 20348.5020 (Server 2022), 25398.2274 (Server 2022 23h2), or 26100.32690 (Server 2025)
-
Verify WalletService presenceRun 'Get-Service WalletService' in PowerShell or check Services.msc for a service named WalletServiceAffected if WalletService is installed and listed as an available service on the system
-
Confirm WalletService statusRun 'Get-Service WalletService' or check the service status in Services.mscAffected if WalletService is in a Running or Started state, making it actively exposed to potential exploitation
-
Check for recent security updatesRun 'Get-HotFix | Where-Object {$_.Description -eq "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10' to list recent security patchesAffected if No recent security updates addressing this CVE are installed, or the installed update KB is unknown
If the Windows Server build is below the threshold for your version AND WalletService is running, the environment is potentially affected by this use-after-free vulnerability.
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.906010.0.17763.864410.0.20348.5020
Apply vendor-supplied Windows security updates for WalletService; review and restart the affected service; verify no unauthorized privilege escalation has occurred.
Windows Server 2016: build 10.0.14393.9060 or later | Windows Server 2019: build 10.0.17763.8644 or later | Windows Server 2022: build 10.0.20348.5020 or later | Windows Server 2022 23h2: build 10.0.25398.2274 or later | Windows Server 2025: build 10.0.26100.32690 or later
- Identify the current Windows Server build version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which Windows Server version is running (2016, 2019, 2022, 2022 23h2, or 2025) from the build number
- If the build is below the fixed version for your Windows Server version, open Settings > Update & Security > Windows Update
- Click 'Check for updates' to download and install the security patch containing the CVE-2026-32080 fix
- Alternatively, manually install the corresponding KB update from the Microsoft Update Catalog once available
- After installation, verify the new build version matches or exceeds: 10.0.14393.9060 (Server 2016), 10.0.17763.8644 (Server 2019), 10.0.20348.5020 (Server 2022), 10.0.25398.2274 (Server 2022 23h2), or 10.0.26100.32690 (Server 2025)
- Restart the server to complete the patch installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32080 — 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-32080 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