Skip to main content

Bind Filter Driver CVE-2026-83852

| EUVDEUVD-2026-99388 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-xvp3-qffw-hgrw
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local foothold
  2. Delivery
    Issue crafted requests to Bind Filter Driver
  3. Exploit
    Trigger use-after-free race window
  4. Execution
    Reclaim freed kernel object with controlled data
  5. Persist
    Corrupt kernel memory for arbitrary execution
  6. 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

Exploitation requires the attacker to already possess authenticated, low-privileged local code execution on the target Windows system (AV:L, PR:L) - this is a post-compromise privilege-escalation flaw, not a remote entry vector. The limiting factors are significant: high attack complexity (AC:H) because the use-after-free is a race condition demanding a precisely timed kernel object reclaim, no remote network reachability, and the need for valid local access. No special non-default configuration is indicated; the Bind Filter Driver is a standard Windows component, so default installations of the listed builds (Windows 11 24H2/25H2/26H1/26H2 and Windows Server 2025, including Server Core) are affected unless patched to the fixed revisions.

Impact

This is a genuine but second-tier priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N) describes a local privilege-escalation flaw requiring the attacker to already have low-privileged authenticated code execution on the host, and the high attack complexity (AC:H) reflects the race-condition nature typical of a use-after-free (CWE-416) in a kernel driver - the attacker must win a timing window to reliably corrupt freed memory. The signals are consistent and point AWAY from mass exploitation: there is no CISA KEV listing, no public POC referenced, and CISA's SSVC decision explicitly records Exploitation=none and Automatable=no, which agrees with the AC:H / local-only / authentication-required profile. The one signal pulling upward is SSVC Technical Impact=total, matching the CVSS C:H/I:H/A:H (kernel compromise yields full SYSTEM control). Net: a reliable kernel EoP primitive valuable as a post-compromise building block (e.g., sandbox escape or chaining after initial foothold), but not a drive-by or wormable threat. Patch is available from Microsoft, so remediation is straightforward.

Exploit ScenarioDerived

An attacker who has already achieved low-privileged code execution on a Windows host (e.g., via phishing or an exploited user-mode application) interacts with the Bind Filter Driver to trigger a use-after-free, winning a race condition to reclaim the freed kernel object with attacker-controlled data. Successful exploitation corrupts kernel memory and elevates the process to SYSTEM. No public exploit code was identified at the time of analysis, and the high attack complexity means reliable exploitation requires precise timing.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% 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 (bflt.sys), a core kernel-mode component, allows an authenticated low-privileged attacker with existing code execution on a target host to escalate to SYSTEM-level privileges through a use-after-free condition (CWE-416). Exploitation is not trivial: the flaw is a race condition requiring precisely timed reclamation of a freed kernel object, reflected in the high attack-complexity rating of the assessed vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H (CVSS 7.0), and the attacker must already hold local access (AV:L, PR:L) - this is a post-compromise escalation primitive, not a remote entry vector. No public exploit code was identified and CISA's SSVC assessment records exploitation as none, so this is a genuine but second-tier priority relative to actively exploited kernel flaws; it nonetheless affects default installations of Windows 11 24H2/25H2/26H1/26H2 and Windows Server 2025 (including Server Core) until patched.

RemediationAI

Vendor-released patch: Microsoft has published an update for CVE-2026-83852 through the Microsoft Security Update Guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83852); apply the current cumulative security update for each affected branch so that systems reach or exceed the fixed builds cited in the EUVD data - 10.0.26100.9711 for Windows 11 24H2, 10.0.26200.9711 for 25H2, 10.0.26300.9711 for 26H2, 10.0.28000.3231 for 26H1, and 10.0.26100.33650 for Windows Server 2025 and its Server Core installation. The single most effective compensating control is to eliminate the precondition: this flaw requires an attacker to already hold authenticated, low-privileged local code execution, so hardening endpoints against initial local footholds - removing unnecessary local admin rights, blocking execution of user-writable binaries and script hosts via WDAC/AppLocker, and constraining interactive/RDP access - directly reduces exposure. There is no practical way to disable the Bind Filter Driver itself; it is a standard kernel component underpinning storage and device binding, and attempting to unload or block bflt.sys would break device and storage functionality on the host, so that trade-off is not advisable. If the update cannot be deployed immediately, prioritize it on multi-user and session-host systems such as Remote Desktop Services and VDI hosts where low-privileged local access is routinely available to untrusted users, and use kernel-level exploitation telemetry (for example, monitoring for unexpected SYSTEM-level token acquisition, anomalous driver object manipulation, and crash patterns originating from bflt.sys) to detect attempts pending remediation.

Affected VersionsENISA

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

Affected Packages

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 6 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 (bflt.sys) is a standard Microsoft kernel-mode filter driver that participates in the Windows bind/miniport/storage filtering stack and loads by default, which is why a fault in it is reachable on default builds rather than requiring optional configuration. The root cause class is CWE-416, use-after-free: a kernel object is released while a reference to it remains live, and the dangling reference can then be exercised after the memory has been reallocated with attacker-influenced contents. Because the vulnerable code runs in kernel mode (ring 0), turning that dangling reference into controlled execution or an arbitrary read/write yields full local privilege escalation and, per the SSVC technical-impact rating of 'total', potentially complete loss of confidentiality, integrity, and availability on the affected host. The assessed vector's AC:H is the key technical qualifier: this is a race window rather than a deterministic bug, so a successful exploit generally demands heap grooming and carefully timed object reclaim under churn, which is why exploitation is characterized as difficult and not automatable (SSVC Automatable: no). The evaluated builds span the Windows 11 servicing branches 24H2 (10.0.26100.x), 25H2 (10.0.26200.x), 26H1 (10.0.28000.x), and 26H2 (10.0.26300.x), plus Windows Server 2025 and its Server Core installation (10.0.26100.x).

Know when the next one hits your stack

  • 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 kernel EoP by an authenticated low-priv user (AV:L/PR:L), with AC:H for the use-after-free race condition; 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

A high-severity flaw in the Windows Bind Filter Driver (bflt.sys), a kernel-mode component present in default installations of Windows 11 24H2/25H2/26H1/26H2 and Windows Server 2025 including Server Core, could allow an attacker who has already gained a foothold on a machine to elevate from a low-privileged account to full SYSTEM control. This is not a remote entry point - it requires an existing compromise plus precise timing to trigger - so it functions as a force multiplier that turns a limited foothold into full host takeover, making timely patching of estate-wide Windows endpoints and servers the priority. No public exploit code has been identified, so this is a genuine but second-tier risk relative to actively exploited kernel vulnerabilities.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Ubiquitous
core Windows OS component across all supported client and server builds
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
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.2%
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.

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