Patch tracker / CVE reference / CVE-2026-62832

CVE-2026-62832

Improper link resolution before file access ('link following') in Windows User Profile Service allows an authorized attacker to elevate privileges locally.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Vulnerability, CVSS 7.8 (High).

How to fix CVE-2026-62832 Change history Admin questions

Risk summary

High

7.8

CVSS v3 base

High

Severity

Not listed

Actively exploited

Schedule normally

No exploitation observed as of 2026-11-01: not in the CISA KEV catalog, EPSS under 1%.

The vendor has published an advisory with the fix: the vendor advisory.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Updated August 11, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.

Senserva AI Opinion and rich prompt for CVE-2026-62832

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-62832 (source: https://senserva.com/cve/CVE-2026-62832.html, data from CISA KEV and NVD, refreshed daily (early morning US Central)):
- CVE-2026-62832: High severity vulnerability, CVSS 7.8
- Actively exploited (CISA KEV): no
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for CVE-2026-62832

Published: 2026-08-11
Last revised: 2026-08-11
Changes tracked: 1

Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.

How to fix CVE-2026-62832

Update Microsoft Windows 10 21h2 to version 10.0.19044.7663 or later. Update Microsoft Windows 10 22h2 to version 10.0.19045.7663 or later. Update Microsoft Windows 11 23h2 to version 10.0.22631.7517 or later. (Fixed-version data from NVD.) Where a workaround exists, apply it only until the update is deployed, not as a substitute.

Vendor advisory NVD detail

Common questions about CVE-2026-62832

Is CVE-2026-62832 actively exploited?

It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. That can change: unexploited CVEs regularly get weaponized months after disclosure, which is why patching on your normal cadence matters.

What fixes CVE-2026-62832?

Update Microsoft Windows 10 21h2 to version 10.0.19044.7663 or later. Update Microsoft Windows 10 22h2 to version 10.0.19045.7663 or later. Update Microsoft Windows 11 23h2 to version 10.0.22631.7517 or later. Fixed-version data from NVD; the vendor advisory linked on this page has the details.

Which products are affected by CVE-2026-62832?

See the vendor security advisory for the affected product list.

Can I ask my own AI about CVE-2026-62832?

Yes. This page includes a free, ready-to-paste AI prompt with CVE-2026-62832's key facts: severity, CVSS, CISA KEV status, and the affected products. Copy it into Claude, ChatGPT, or Copilot for a triage plan.

Scope and sources

Authoritative references: CVE record NVD detail

Every Microsoft CVE and the patches that fix it, ranked by real-world risk: the Microsoft Patch Tracker. The full searchable CVE reference: CVE and vulnerability management.