Security readout for executives and security teams
Plain-English summary
This flaw could let an unauthenticated attacker on a nearby network execute code on a Windows Server running Windows Deployment Services. Successful exploitation could compromise sensitive data, alter systems, or disrupt service. Exploitation is described as difficult, but no user action or existing account is required.
Executive priority
Treat this as a high-priority infrastructure remediation, especially for deployment servers accessible from less-trusted network segments. Schedule Microsoft updates promptly after operational testing. Immediate emergency action is not supported solely by the supplied evidence because active exploitation is not reported and exploitation complexity is high.
Technical view
CVE-2026-0386 is an improper access-control vulnerability in Windows Deployment Services. It permits remote code execution from an adjacent network with high attack complexity, no privileges, and no user interaction. CVSS 3.1 rates it 7.5, with high potential impact to confidentiality, integrity, and availability.
Likely exposure
Potential exposure spans listed Windows Server releases from 2008 through 2025, including multiple Server Core installations. Practical risk is greatest where Windows Deployment Services is installed, active, and reachable from adjacent network segments. The supplied sources do not establish exposure beyond the listed versions.
Exploitation context
The source bundle does not identify active exploitation, and the CVE is not listed as KEV. Microsoft reports adjacent-network access and high attack complexity, reducing reachability and reliability compared with internet-routable flaws. However, attackers need neither authentication nor user interaction.
Researcher notes
The stated weakness is CWE-284. The vector is AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, with remediation available according to the vendor-reference tag. The bundle provides no exploit method, detection indicators, affected-component internals, or exact update identifiers; consult the live Microsoft advisory for those details.
Mitigation direction
- Review Microsoft’s advisory and apply the applicable security update for each affected server.
- Prioritize servers running Windows Deployment Services and reachable from less-trusted adjacent networks.
- Restrict adjacent-network access to Windows Deployment Services where operationally feasible.
- If updates cannot be applied promptly, check Microsoft guidance for supported mitigations or service-disabling options.
Validation and detection
- Inventory listed Windows Server versions and Server Core installations.
- Confirm whether Windows Deployment Services is installed and active on each candidate server.
- Map which adjacent network segments can reach affected deployment servers.
- Verify the applicable Microsoft security update is installed successfully.
- Reassess exposure after remediation and document any accepted exceptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-0386 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.65.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Deployment Services Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.