cve.bz

CVE-2026-0386 microsoft: Improper Access Control

7.5 highEPSS 0.5%

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

On this page
Improper access control in Windows Deployment Services allows an unauthorized attacker to execute code over an adjacent network.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 47th percentile. Scored 2026-11-21. 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-01-14. 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-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-0386 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-0386?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-0386?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-0386 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 2008 R2 Service Pack 1from 6.1.7601.0 before 6.1.7601.28117
Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)from 6.1.7601.0 before 6.1.7601.28117
Microsoft Windows Server 2008 Service Pack 2from 6.0.6003.0 before 6.0.6003.23717
Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)from 6.0.6003.0 before 6.0.6003.23717
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.25868
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.25868
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.22968
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.22968
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.8783
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.8783
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.8276
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.8276
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.4648
Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)from 10.0.25398.0 before 10.0.25398.2092
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.32230
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.32230

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON