Skip to main content

Bind Filter Driver EUVDEUVD-2026-100034

| CVE-2026-83900 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-7g8f-8cm4-p2fg
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Exploit
    Trigger use-after-free race in Bind Filter Driver
  3. Execution
    Execute code in kernel context
  4. Impact
    Elevate to SYSTEM privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the attacker to already have authenticated, low-privileged local code execution on the target Windows host (PR:L, AV:L) - there is no remote or network path. Exploitation further depends on triggering the use-after-free in the Bind Filter Driver (bindflt), which the high attack complexity (AC:H) indicates requires winning a race condition or achieving a specific memory-reuse timing, not a deterministic single-shot trigger. No user interaction is needed (UI:N). The combination of mandatory local foothold plus the unreliable race-dependent trigger meaningfully limits real-world exploitation to post-compromise escalation scenarios. Affected builds are specific: Windows 11 (23H2 through 26H2) and Windows Server 2025 below the fixed build numbers listed in EUVD; patched builds are not exploitable.

Impact

Signals here are consistent and point to a genuine but not emergency-grade priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0) describes a local privilege-escalation requiring an already-authenticated low-privileged user and a high-complexity trigger - consistent with a use-after-free (CWE-416) that depends on winning a race or precise heap state. CISA's SSVC decision data reinforces the lower urgency: Exploitation=none (no observed exploitation), Automatable=no (cannot be mass-scripted, fitting the local AV and high AC), but Technical Impact=total (full kernel compromise if achieved). No EPSS score is provided in the input, so exploitation probability cannot be quantified. This is NOT in CISA KEV and no public POC is indicated, so it is not under active exploitation. The practical reading: a credible post-compromise escalation vector worth patching in normal cycles, but not a drop-everything internet-facing emergency - its value to an attacker is as a second-stage tool after they already have a foothold, not as an initial breach vector.

Exploit ScenarioDerived

An attacker who already has low-privileged code execution on a Windows host (e.g., via phishing or a compromised standard user account) runs a crafted local program that manipulates the Bind Filter Driver to trigger the use-after-free, winning the timing race required by the high attack complexity. Successful exploitation corrupts kernel memory and yields SYSTEM-level privileges, enabling full host compromise. No public exploit identified at time of analysis, and CISA SSVC lists exploitation as none.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in the Windows Bind Filter Driver (bindflt.sys) allows an attacker who already holds authenticated, low-privileged code execution on a Windows host to corrupt kernel memory and elevate to SYSTEM. The flaw is a use-after-free (CWE-416) requiring a race-condition-style trigger, reflected in the CVSS vector AV:L/AC:H/PR:L/UI:N (7.0 High) and the CISA SSVC assessment of Exploitation: none and Automatable: no - there is no remote path, no user interaction, and no public exploit identified at time of analysis. It was not added to CISA KEV, and vendor-supplied patches are available; affected builds are specific Windows 11 23H2 through 26H2 releases and Windows Server 2025 (including Server Core) below the fixed build numbers, while patched builds are not exploitable. Independent assessment rates this as a genuine but not emergency-grade priority best handled through routine monthly patching.

RemediationAI

Vendor-released patch: Microsoft addresses this in the update-guide entry for CVE-2026-83900 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83900); apply the applicable cumulative update so hosts reach at least Windows 11 23H2 build 10.0.22631.7652, 24H2 build 10.0.26100.9711, 25H2 build 10.0.26200.9711, 26H1 build 10.0.28000.3231, 26H2 build 10.0.26300.9711, or Windows Server 2025 / Server Core build 10.0.26100.33650, and prioritize servers that host Windows containers since they are the most likely to exercise bindflt.sys. Because exploitation requires an existing authenticated low-privileged local foothold, the highest-value compensating control against unpatched hosts is reducing the local attacker surface - enforce least privilege, restrict interactive logon and RDP on container hosts, and remove or tightly scope local administrative group membership - while treating the AC:H race requirement as a partial, not reliable, barrier. A stronger but disruptive workaround is to stop and disable the driver itself (sc stop bindflt and sc config bindflt start=disabled, or restrict loading via driver blocklist policy); the trade-off is that container bind/mount functionality and any workload relying on bindflt-based volume redirection will fail until re-enabled. Kernel-level monitoring for unexpected bugchecks or abnormal bindflt.sys pool activity can provide detection coverage, and hosts should be rebooted after patching because kernel driver fixes require a restart to take effect.

Affected VersionsENISA

Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711

Affected Packages

euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 7 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The Bind Filter Driver (bindflt) is a Microsoft-supplied file system filter driver that supports bind mounts and volume redirection, most commonly surfaced through Windows container scenarios where host directories are mapped into container namespaces. Because it runs in kernel mode and parses/manages redirected path and volume state, an error in its object lifetime management permits a use-after-free (CWE-416): memory associated with a filter context can be released while still referenced, and the freed region can then be reclaimed and manipulated by the attacker. Exploitation is gated by high attack complexity (AC:H), indicating the attacker must win a timing/race window or arrange precise memory reuse rather than triggering the bug deterministically in a single request. The associated tags (Use After Free, Memory Corruption, Denial Of Service, Microsoft) are consistent with a kernel-pool lifetime bug that can crash the system if the timing is wrong, but that yields full read/write influence on the C:I:H/I:H/A:H dimensions when the timing succeeds. The affected code path is reachable only from the local machine (AV:L), and the required privilege level is low (PR:L), so the realistic attack model is post-compromise escalation inside a kernel driver rather than an initial remote intrusion vector.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local-only driver flaw needing authenticated low-priv access (AV:L/PR:L); use-after-free race gives AC:H; successful kernel compromise yields full C/I/A impact.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Bind Filter Driver allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

The Windows Bind Filter Driver (bindflt.sys) privilege-escalation issue affects Windows 11 23H2 through 26H2 and Windows Server 2025 (including Server Core), allowing an authenticated low-privileged local attacker to elevate to SYSTEM on unpatched hosts. For the organization, this raises the risk that an existing foothold on a managed endpoint or server could be turned into full host control, enabling credential theft, persistence, and lateral movement. No public exploit was identified at time of analysis, the issue is not in CISA KEV, and the patch is available per vendor advisory, so leadership should treat it as a prioritized routine-patching item rather than an emergency incident.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 82% exploitable
Prevalence
Ubiquitous
Core Windows kernel driver present across virtually all Windows deployments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy