nday
CVE-2026-81963

Windows Update Stack Elevation of Privilege Vulnerability

Microsoft / Windows, Windows 11 version 23H2, Windows 11 Version 24H2, Windows 11 Version 25H2, Windows 11 version 26H1, Windows Server 2025 +1

Added to CISA KEV on the day of disclosure. nday has no fix record for it yet; that does not mean no patch exists. None of the four PoC sources lists it.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

broken access control
CWE-284, stated by the CNA microsoft and NVD, republishing [email protected]
link following
CWE-59, stated by the CNA microsoft and NVD, republishing [email protected]
local
AV:L in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
no user interaction
UI:N in CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C (CVSS 3.1) from the CNA microsoft
Windows
affected products in the CVE record: Microsoft · Windows, Microsoft · Windows 11 Version 23H2, Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 Version 25H2, Microsoft · Windows 11 version 23H2, Microsoft · Windows 11 version 26H1CPE names NVD's analysts give as vulnerable: o:microsoft:windows_11_23h2, o:microsoft:windows_11_24h2, o:microsoft:windows_11_25h2, o:microsoft:windows_11_26h1
Windows Server
affected products in the CVE record: Microsoft · Windows Server 2025, Microsoft · Windows Server 2025 (Server Core installation)CPE names NVD's analysts give as vulnerable: o:microsoft:windows_server_2025
operating system
affected products in the CVE record: Microsoft · Windows, Microsoft · Windows 11 Version 23H2, Microsoft · Windows 11 Version 24H2, Microsoft · Windows 11 Version 25H2, Microsoft · Windows 11 version 23H2, Microsoft · Windows 11 version 26H1, Microsoft · Windows Server 2025, Microsoft · Windows Server 2025 (Server Core installation)CPE names NVD's analysts give as vulnerable: o:microsoft:windows_11_23h2, o:microsoft:windows_11_24h2, o:microsoft:windows_11_25h2, o:microsoft:windows_11_26h1, o:microsoft:windows_server_2025the product type of Windows and Windows Server in nday's product registry
stage
KEV
disclosed
cvss
7.8 HIGH v3.1
KEV due date
2026-09-22

Lifecycle

x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
09-08T17:19Z
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
≤ 09-08, inferred from KEV
KEVKEV
09-08, date only

Summary

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

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:L
Low: no special conditions; the attacker can expect repeatable success
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

CVSS 3.1 vector from the CVE record, scored by the CNA microsoft.

Event log

2026-09-08date only, from source
+KEVadded to KEV

CISA added it to the Known Exploited Vulnerabilities catalog, with a remediation deadline of 2026-09-22. Ransomware use: unknown.

src kev · nday , bulk import · raw
{
  "id": 82,
  "type": "kev_added",
  "source": "kev",
  "url": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog",
  "occurred_at": "2026-09-08T00:00:00Z",
  "observed_at": "2026-11-12T13:53:00.018191Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "cwes": [
      "CWE-59",
      "CWE-284"
    ],
    "notes": "https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-81963 ; BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk ; Forensics Triage Requirements: https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk ; https://nvd.nist.gov/vuln/detail/CVE-2026-81963",
    "product": "Windows",
    "due_date": "2026-09-22",
    "precision": "day",
    "date_added": "2026-09-08",
    "vendor_project": "Microsoft",
    "forensic_triage": "No",
    "required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.",
    "vulnerability_name": "Microsoft Windows Link Following Vulnerability",
    "known_ransomware_campaign_use": "Unknown"
  }
}
≤ 2026-09-08inferred, no direct source
~ITWexploited in the wild

No source says when exploitation began. A KEV listing means it was already happening, so only an upper bound is known. CISA's SSVC assessment rates exploitation as active.

based on kev and CISA's assessment in cvelist

+DISdisclosed

CVE record published by microsoft. CVSS 7.8, high. CISA's SSVC assessment rates exploitation as active.

src cvelist · nday , bulk import · raw
{
  "id": 15019,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-81963",
  "occurred_at": "2026-09-08T17:19:13.121Z",
  "observed_at": "2026-11-12T14:10:31.286634Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "kev": {
      "reference": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-81963",
      "date_added": "2026-09-08"
    },
    "cvss": {
      "source": "cna",
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C",
      "version": "3.1",
      "base_score": 7.8,
      "base_severity": "HIGH"
    },
    "ssvc": {
      "timestamp": "2026-09-07T00:00:00+00:00",
      "automatable": "no",
      "exploitation": "active",
      "technical_impact": "total"
    },
    "state": "PUBLISHED",
    "date_published": "2026-09-08T17:19:13.121Z",
    "assigner_short_name": "microsoft"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Researcher discussion

0 researchers mentioned this in the last 7 days

Posts on X by researchers on nday's list that mention this CVE, shown as posted. nday does not check them.

nday has not collected any post on X by listed researchers that mentions this CVE.

Discussion

0 comments

No comments yet.