External risk intelligence

Windows iSCSI Target Service Heap Overflow Remote Code Execution

CVE advisorySeverity: CRITICAL (CVSS 9.8)

CVE-2026-65791

The Windows iSCSI Target Service is designed for storage area networking, which is typically restricted to internal, isolated, or backend network segments rather than being exposed directly to the public internet. While it operates over a network, its deployment pattern generally necessitates significant architectural controls that prevent public internet reachability.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in the Windows iSCSI Target Service could allow an unauthorized attacker to execute code over a network. This type of issue can be serious because it affects a core operating system component and has the potential for remote exploitation. The primary concern is to confirm if this specific service is in use and potentially exposed within your environment.

  • Attacker can run code remotely.
  • Affects a core Windows service.
  • Confirm relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker could exploit this vulnerability by sending specially crafted network traffic to the Windows iSCSI Target Service. This service, when exposed to a network, could be targeted by an unauthorized attacker without requiring any user interaction or privileges. Successful exploitation could allow the attacker to execute arbitrary code on the affected system.

  • Attack starts from the network.
  • Vulnerable iSCSI Target Service is triggered.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

A heap-based buffer overflow in the Windows iSCSI Target Service could allow an unauthenticated attacker to execute code remotely over a network, potentially impacting the availability and integrity of the affected system. This vulnerability could be exploited when the iSCSI Target Service is accessible over a network.

  • System services and data.
  • Remote code execution over network.
  • System compromise and data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in the Windows iSCSI Target Service likely falls under the responsibility of infrastructure or platform teams managing Windows Server environments. The first practical step is to identify all instances of the iSCSI Target Service, determine their network exposure, and assess their business criticality. This will help in prioritizing remediation efforts and engaging the appropriate system owners.

  • Infrastructure/Platform teams own the issue.
  • Verify iSCSI Target Service exposure and criticality.
  • Plan remediation based on risk assessment.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the Windows iSCSI Target Service?

The Windows iSCSI Target Service is a built-in feature of Windows Server that enables a machine to act as a storage server. It allows other computers on a network to connect to and use the server's storage as if it were a local disk, a technique commonly used in data centers to manage shared storage resources.

What does CWE-122 mean for CVE-2026-65791?

CWE-122 refers to a heap-based buffer overflow. This is a memory management weakness where an application tries to write more data into a reserved memory area, or heap, than it can hold. In the context of CVE-2026-65791, this flaw allows an attacker to overwrite adjacent memory, potentially leading to unauthorized code execution.

How is this vulnerability triggered?

An attacker triggers this bug by sending specially crafted network traffic directly to the iSCSI Target Service. The vulnerability does not rely on specific user actions or pre-existing authentication. Simply having the service reachable over a network is sufficient for an attacker to attempt the exploit.

Do I need to worry about this if my server is internal?

While the vulnerability is serious, Halo Surface Signal notes that the iSCSI Target Service is typically found in isolated backend networks rather than on the public internet. If your service is restricted to an internal, non-public network segment, the likelihood of a remote attacker reaching it is significantly lower than for internet-facing systems.

When should I take action for this vulnerability?

You should prioritize this by first verifying if the iSCSI Target Service is enabled on your servers. Once identified, evaluate the network accessibility of those machines to determine the actual risk. If the service is active, coordinate with your infrastructure team to review security configurations and apply necessary updates once they become available.

References