Security readout for executives and security teams
Plain-English summary
A person who already has authorized local access to an affected Windows computer could exploit a memory-handling flaw to gain higher privileges. Successful exploitation could enable full compromise of that computer’s confidentiality, integrity, and availability. This is serious, but the supplied sources do not establish remote exploitation or exploitation in the wild.
Executive priority
Treat this as a high-priority patching issue, especially where many users, contractors, or workloads have local access. It is not evidenced as an internet-origin attack or active exploitation, so prioritize promptly through normal high-severity remediation rather than declaring an emergency solely from this bundle.
Technical view
CVE-2026-35418 is a local elevation-of-privilege vulnerability in the Windows Cloud Files Mini Filter Driver. The bundle identifies use-after-free and race-condition weaknesses (CWE-416 and CWE-367). Exploitation requires low privileges, has low complexity, needs no user interaction, and retains the same security scope. CVSS 3.1 rates it 7.8.
Likely exposure
Potential exposure includes the listed Windows 10, Windows 11, Windows Server 2019, Server 2022, and Server 2025 releases, including specified Server Core editions. The supplied version numbers identify affected product baselines but do not provide fixed-build thresholds. Confirm exposure against Microsoft’s current affected-product and update tables.
Exploitation context
The attack is local and requires an authorized, low-privileged attacker. No user interaction is required. The bundle reports no CISA KEV listing, and its CVSS exploit-maturity value is unproven. Therefore, active exploitation and public exploit availability should not be claimed from this evidence.
Researcher notes
The supplied evidence supports a memory-lifetime flaw involving use-after-free and a race condition, but it provides no triggering conditions, affected function, exploit primitive, fixed-build thresholds, or named update identifiers. Researchers should use Microsoft’s advisory for authoritative build and patch details and avoid inferring remote reachability or exploitation status.
Mitigation direction
- Consult Microsoft MSRC for the applicable security update and deploy it to affected systems.
- Prioritize systems accessible to lower-trust local users or compromised accounts.
- Restrict unnecessary local and interactive access until affected systems are updated.
- Monitor Microsoft’s advisory for revisions, affected-build changes, and updated remediation guidance.
Validation and detection
- Inventory the listed Windows releases and record their exact builds and servicing status.
- Compare each system with Microsoft’s current affected-product and security-update tables.
- Verify the applicable Microsoft security update is installed through endpoint-management records.
- Re-scan updated systems for CVE-2026-35418 and investigate unresolved findings.
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-367: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCWE-416: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-35418 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.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/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:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/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 Cloud Files Mini Filter Driver Elevation of Privilege 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.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.