WINDOWS FILE SERVER RESOURCE MANAGEMENT SERVICE · CVE-2026-113765 · Infrastructure
NO FIX YET
A heap-based buffer overflow in the Windows File Server Resource Management Service lets an authorized local user raise their privileges. Exploitation requires that the attacker already has a valid account on the machine.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Windows Servers running the File Server Resource Management service (FSRM, part of the File Server role) are the systems to look at. The sources do not say which Windows builds or configurations are affected, and the attacker must already be authorized on the machine. Systems without the FSRM role installed are likely not exposed, but the sources do not confirm this.
Not affected if fsrm-not-installed
Who cares file-server, windows, windows-server
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Heap-based buffer overflow in Windows File Server Resource Management Service allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.