cve.bz

CVE-2026-105009 microsoft: Incorrect Default Permissions

7.5 highEPSS 0.3%Fix available

High (7.5) in microsoft. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Incorrect default permissions in Windows Server Update Service allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-16. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-276 Incorrect Default Permissions
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-105009 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105009?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105009?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105009 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.26434
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.26434
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.23470
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.23470
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.9612
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.9612
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.9376
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.9376
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.5761
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33650
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.33650

Attack patterns (CAPEC)

  • CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
  • CAPEC-81 Web Server Logs Tampering Likelihood: Medium · Severity: High
  • CAPEC-127 Directory Indexing Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON