On this page (8 sections)

CVE-2026-96951 is a command injection flaw in Windows Shell that lets an unauthorized attacker bypass a security feature over a network. A Patch Tuesday forecast published by Help Net Security describes it as the one October 2026 zero-day confirmed as exploited, and CISA added it to its Known Exploited Vulnerabilities catalog on 2026-10-13.

If you administer Windows 10, Windows 11 or Windows Server machines, including the servers and admin workstations that sit behind your websites, look up the update Microsoft lists in its advisory for this CVE and confirm it is installed. The sources do not name that update or its release date, so the advisory is the place to start. Several other items from the same forecast, such as the PHP issue relevant to web servers, are summarized below.

What happened

The Help Net Security forecast reports that Microsoft's October 2026 Patch Tuesday resolved 1,407 unique CVEs, 78 of them rated Critical. Against that volume, CVE-2026-96951 stood out because it was the one zero-day in October confirmed as exploited, described as a Windows Shell security feature bypass affecting Windows 10, Windows 11 and Windows Server.

CISA's catalog entry describes it as a command injection vulnerability in Microsoft Windows Shell. It set a due date of 2026-10-16 for US federal agencies and marked forensic triage as required under its BOD 26-04 directive. Whether the flaw has been used in ransomware campaigns is listed as unknown.

The sources confirm exploitation and link to a Microsoft advisory tagged as a patch, but they do not say which update fixes the flaw or when it shipped. Do not assume a particular monthly update covers it; confirm against Microsoft's advisory.

Technical details

CWE-77 describes software that builds all or part of a command from externally influenced input without properly neutralizing special characters, so the input can change what the command does. In plain terms, data that should be treated as inert text ends up interpreted as part of an instruction.

The CVSS vector in the GitHub advisory is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. That means it is reachable over a network, has low attack complexity, needs no privileges, and requires user interaction, with high impact on confidentiality, integrity and availability. The user interaction requirement suggests a person must do something, such as open or interact with attacker-supplied content. The sources do not describe the exact trigger, and this article does not speculate about one.

The same advisory lists an EPSS score of 9.813% (96th percentile), an estimate from FIRST of the likelihood of exploitation in the next 30 days. Since exploitation is already confirmed, treat that figure as secondary.

Who is affected

Based on the sources, the exposure is Windows 10, Windows 11 and Windows Server systems that have not installed the update Microsoft lists for this CVE. The GitHub advisory lists affected and patched versions as unknown, so Microsoft's advisory page is the place to confirm the exact update for each build.

For website owners, the realistic exposure is not the public website itself but the Windows machines around it: admin workstations, jump hosts, and Windows servers running IIS or management tools. A compromised admin workstation can expose hosting panels, credentials and deployment pipelines.

How to check your exposure

First find the update Microsoft names for your Windows version in its advisory for CVE-2026-96951. Then run this read-only PowerShell command on the Windows machine. It lists installed updates with their install dates, so you can look for the KB number from the advisory.

List installed Windows updates, newest first (run in PowerShell on each Windows host)PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 15 HotFixID, Description, InstalledOn

If the KB listed by Microsoft for your Windows version is not in the output, the machine is not yet patched for this issue. If you manage many machines, use your update management tool's compliance report instead of checking one by one.

What to do now

  1. Open the Microsoft advisory for CVE-2026-96951 and note the update for each Windows version you run.
  2. Install that update on all affected Windows 10, Windows 11 and Windows Server systems, starting with internet-facing servers and admin workstations.
  3. Reboot where the update requires it and confirm the update shows as installed.
  4. Because exploitation is confirmed, review recent activity on exposed Windows systems for anything unexpected, such as new accounts, scheduled tasks or unfamiliar processes. CISA flagged forensic triage as required for its agencies.
  5. Remind staff not to open unexpected files or links, since the flaw needs user interaction.
  6. Keep applying monthly Windows updates. The forecast says the out-of-band and preview security fixes from October will be included in the November Patch Tuesday cumulative release.
Caution. Installing Windows updates usually requires a restart. Schedule it for a maintenance window on production servers, and take a backup or snapshot first.

Other items from the November forecast

The same Help Net Security column covers several issues that matter to people who run websites. These are the author's summaries, and you should confirm details in the vendor advisories.

  • PHP (CVE-2026-109618 and CVE-2026-109619, called PHP2Shell by researchers): PHP published an advisory on October 21. The column says exploitation in the wild began several days before patches and is expanding. It notes that you must replace the PHP runtime and restart the web server, because without a restart the old code stays in memory.
  • Brotli (CVE-2026-111497, also called Broccoli2Shell, Node2Shell or HTTP2Shell): Microsoft issued an emergency fix on October 25 for libraries in .NET 8, 9, 10 and Release Candidate 3 of .NET 11. The column says proof-of-concept code exists but there is no known exploitation in the wild.
  • Certificate trust: on October 26 Microsoft removed seven certificates from the Windows trust list, six eMudhra G3 roots and an AAA Certificate Services cross-sign, because the keys had been compromised, according to the column.
  • Obsolete software: the column describes an abandoned 2014 application still trying to update itself on 2.5 million Windows devices and 300,000 Macs, contacting domains that were open for registration. It was removed before abuse, but it is a reminder to inventory and remove end-of-life software.
Tip. If your sites run on PHP, check your PHP version against the October 21 advisory and restart PHP-FPM or the web server after updating. A package update alone may not replace code already loaded in memory.

Detection and monitoring

Patching closes the known hole, but it does not tell you whether a machine was already compromised. Review endpoint security logs from before the update date, and prioritize hosts that handle credentials or deploy to your sites.

For the web side, watch for unexpected certificate changes and DNS changes on your domains, which can follow a compromise of an admin machine. A certificate and DNS monitoring service and the free SSL checker can help you notice changes quickly. If you suspect a site was altered, follow the steps in website hacked: what to do.

Timeline

Dates as stated in the sources
DateEvent
2026-10-13CVE-2026-96951 published in the GitHub Advisory Database and added to CISA KEV
2026-10-16CISA due date for federal agencies
2026-10-21PHP security advisory for CVE-2026-109618 and CVE-2026-109619 (per Help Net Security)
2026-10-25Microsoft emergency fix for CVE-2026-111497 (per Help Net Security)
2026-10-26Microsoft removes seven compromised certificates from the Windows trust list (per Help Net Security)
2026-11-06Help Net Security publishes the November Patch Tuesday forecast

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. CVE-2026-96951 - GitHub Advisory Databasegithub.com
  2. Known Exploited Vulnerabilities Catalog | CISAcisa.gov
  3. November 2026 Patch Tuesday forecast: Old software continues to bite - Help Net Securityhelpnetsecurity.com ·
  • Windows
  • Patch Tuesday
  • Zero-day
  • CISA KEV
  • CVE-2026-96951