Skip to content
Fencer Intel
high 7.0

CVE-2026-32080 json

Windows WalletService Elevation of Privilege Vulnerability

published 6mo ago modified 14d ago also EUVD-2026-22512

cvss
7.0
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 11%
public exploits
0
none known

Summary

Use after free in Windows WalletService allows an authorized attacker to elevate privileges locally.

Patch / fix

  • Microsoft Windows Server 2016 10.0.14393.9060
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.9060
  • Microsoft Windows Server 2019 10.0.17763.8644
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.8644
  • Microsoft Windows Server 2022 10.0.20348.5020
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.2274
  • Microsoft Windows Server 2025 10.0.26100.32690
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.32690

Is CVE-2026-32080 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
6mo ago

Exploit prediction

0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.