Security alert · Critical
Windows iSCSI: critical remote code execution flaw CVE-2026-88234 (CVSS 9.8)
· 2 minutes read · Centoculus Security Team
Known since
Affected: Windows (iSCSI component); see the Microsoft advisory for the affected versions
What happened
On 10 November 2026 Microsoft published CVE-2026-88234, a vulnerability in the Windows iSCSI component. Microsoft describes it as a release of an invalid pointer or reference. It allows an unauthorized attacker to execute code over a network. The CVSS base score is 9.8 (critical).
As of today (18 November 2026), CISA does not list this vulnerability in its catalogue of known exploited vulnerabilities. Our sources do not document any attacks.
Who is affected
The description names the Windows iSCSI component. It does not mention Microsoft Exchange Server, even though some catalogue data lists the product as Exchange. Our source data does not say which Windows and Windows Server versions are affected or which updates fix the flaw. Microsoft's advisory, linked below, has the authoritative list of affected versions and the matching security updates.
This flaw does not affect Linux servers.
What to do now
- Open Microsoft's advisory for CVE-2026-88234 (linked below) and find the security update for each Windows version you run.
- Install that update on all affected Windows servers using Windows Update, WSUS or your patch management tool. Start with servers that can be reached from untrusted networks.
- Restart the servers if the update asks for it, then check that your services, including any iSCSI storage connections, work again.
- As general hardening, make sure iSCSI traffic (by default TCP port 3260) can only be reached from your dedicated storage network and not from the internet. This limits exposure but does not replace the update.
How to check whether you are affected
- In PowerShell, run
Get-HotFix | Sort-Object InstalledOn -Descendingand compare the installed updates with the ones listed in Microsoft's advisory for your Windows version. - To see whether a server uses iSCSI, run
Get-Service MSiSCSI(iSCSI Initiator service). On Windows Server, also runGet-WindowsFeature FS-iSCSITarget-Server(iSCSI Target Server role). - To see whether the server listens on the default iSCSI port, run
Get-NetTCPConnection -LocalPort 3260 -State Listen -ErrorAction SilentlyContinue. Then check your firewall rules to see which networks can reach that port.
These checks show whether iSCSI is in use or exposed on a server. Whether the server is vulnerable depends on its Windows version and patch level, as listed in Microsoft's advisory.
Sources
More on Microsoft Exchange
- Windows Media Foundation: critical remote code execution flaw (CVE-2026-96157)
- Microsoft Color Management: critical remote code execution flaw (CVE-2026-96078)
- Microsoft Exchange: critical remote code execution via Color Management (CVE-2026-96067)
- Windows DHCP Server: critical remote code execution flaw (CVE-2026-88243)
- Windows DNS CVE-2026-88218: critical remote code execution flaw, CVSS 9.8
- Windows Kerberos CVE-2026-85844: authentication bypass allows privilege escalation
- Microsoft SharePoint: critical privilege escalation flaw (CVE-2026-120002)
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.