What happened
On October 13, 2026, three critical vulnerabilities in Windows components were published in the NVD database. Both the description and the rating come from Microsoft. They affect the Microsoft QUIC library (CVE-2026-105016), OpenSSH for Windows (CVE-2026-97816) and the Windows Error Reporting service (CVE-2026-97815). For all three, Microsoft states that an unauthenticated attacker can run their own code on the machine over the network.
Microsoft publishes the details, affected Windows versions and the matching updates in its Security Update Guide (MSRC) for each of the three flaws. As of November 20, 2026, none of them is in the CISA KEV catalog, and the EU Vulnerability Database EUVD (ENISA) does not list them as exploited. So there are no confirmed attacks so far.
Why it is dangerous
Two of the flaws (QUIC and Windows Error Reporting) are heap-based buffer overflows (CWE-122). Picture glasses on a table: the program pours more into one than it can hold, and the excess spills into the neighbouring ones. An attacker can use this to overwrite data the program relies on later and make it run their own commands.
The OpenSSH for Windows flaw is a use-after-free (CWE-416). The program releases a piece of memory, like handing back a locker key, but later uses it again by mistake. If an attacker has put something into that “locker” in the meantime, the program works with their content.
Microsoft rated all three flaws CVSS 9.8 out of 10 (CVSS version 3.1), which is critical. The rating means:
- the attack works over the network, no physical access needed,
- the attacker needs no login or password,
- the victim does not have to click or open anything,
- the impact on confidentiality, integrity and availability is high: the attacker can run their own code, read and modify data or disrupt the system.
EPSS estimates the probability that a flaw will be exploited within the next 30 days. As of November 19, 2026, it is 1.66% for QUIC, 1.01% for OpenSSH and 0.87% for Windows Error Reporting. These numbers are low, but QUIC scores higher than about 77% of all rated flaws. The CISA KEV catalog lists flaws with confirmed exploitation, and these three are not in it yet.
Who is affected
The NVD records do not list specific affected Windows versions. You will find the exact list of Windows and Windows Server versions in the MSRC advisory for each CVE. As a rough guide to where each component runs:
- Microsoft QUIC: a network library for the QUIC protocol that Windows uses, for example, for HTTP/3 in the IIS web server or for SMB over QUIC. Internet-facing servers are the most exposed.
- OpenSSH for Windows: an optional Windows feature. Microsoft's description does not say whether the server or the client is affected. For a network attack, machines running the SSH server (the
sshdservice) are the most exposed, typically remotely managed servers. - Windows Error Reporting: the error reporting service included in standard Windows installations.
The OpenSSH record refers specifically to OpenSSH for Windows. It does not mention OpenSSH on Linux servers.
How to check if you are affected
The commands below only read information and change nothing. Run them in PowerShell. To find your Windows version and build:
Get-ComputerInfo | Select-Object WindowsProductName, OsBuildNumber
The most recently installed updates, to compare with the KB numbers in the MSRC advisory:
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 10
Whether the SSH server is installed and running (the first command needs admin rights):
Get-WindowsCapability -Online -Name OpenSSH*
Get-Service sshd
The simpler route is Settings > Windows Update > Update history. If you manage machines with WSUS or Intune, check the deployment status of the updates listed in the MSRC advisory.
How to fix it
For each of the three CVEs, Microsoft lists the security updates (KB) for each Windows version in its Security Update Guide. The NVD records do not include patch numbers, so work directly from the MSRC advisories.
Recommended order:
- first, internet-facing servers, especially those running the SSH server or using HTTP/3 and SMB over QUIC,
- then the remaining servers on your internal network,
- finally, workstations.
Steps:
- Open the MSRC advisories for CVE-2026-105016, CVE-2026-97816 and CVE-2026-97815 and find the KB for your Windows versions.
- Take a backup or snapshot before updating a server.
- Install the updates via Windows Update, WSUS or Intune.
- Restart the machine if the update requires it.
- Confirm the installation with
Get-HotFix.
Microsoft does not list a workaround in these records. Until you patch, general measures help: limit SSH access (port 22) to known IP addresses or put it behind a VPN, and if you do not need the SSH server, consider turning it off. The flaws are not in the CISA KEV catalog, so CISA has not set a mandatory patch deadline for them.
What if you may already be compromised
The NVD records contain no indicators of compromise, and no exploitation of these flaws is known so far. If vulnerable servers were reachable from the internet for a long time, it is still worth checking:
- unknown local accounts and new administrators (
Get-LocalUser,Get-LocalGroupMember -SID S-1-5-32-544), - SSH entries in Event Viewer (Applications and Services Logs > OpenSSH > Operational) and logins from unfamiliar IP addresses,
- new services and scheduled tasks you do not recognise,
- unexpected service crashes and unusual outbound network traffic.
If you find anything suspicious, disconnect the server from the network but do not shut it down, so that evidence is preserved. Bring in an incident response specialist.