cve.bz

CVE-2026-96097 Windows Brokering File System Elevation of Privilege Vulnerability

7.0 highEPSS 0.3%

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

On this page
Release of invalid pointer or reference in Windows Brokering File System allows an authorized attacker to elevate privileges locally.

Severity

CVSS 3.1

7.0 high
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 21st percentile. Scored 2026-11-13. 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-11-11. 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-763 Release of Invalid Pointer or Reference
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-96097 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-96097?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-96097?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-96097 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.

Badge for a README or a site

CVE-2026-96097

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-96097](https://cve.bz/cve/badge/CVE-2026-96097.svg)](https://cve.bz/cve/CVE-2026-96097)

HTML:

<a href="https://cve.bz/cve/CVE-2026-96097"><img src="https://cve.bz/cve/badge/CVE-2026-96097.svg" alt="CVE-2026-96097"></a>

Affected

  • microsoft:windows 11 version 24h2
  • microsoft:windows 11 version 25h2
  • microsoft:windows 11 version 26h1
  • microsoft:windows 11 version 26h2

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.9974
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.9974
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.3501
Microsoft Windows 11 Version 26H2from 10.0.26300.0 before 10.0.26300.9974

References

Check your stackJSON