2026-10-26NOTABLEexploitedMicrosoft ships out-of-band .NET fixes: hosts updated on 13 October still carry the Windows sockets flaw
Microsoft Visual Studio
product · product:microsoft-visual-studio single-source
Coverage
2
first 2026-10-07 → last 2026-11-13
Latest activity
2026-11-13
Microsoft ships out-of-band .NET fixes: hosts updated on 13 October still carry the Windows sockets flaw
Peak priority
notable
2 notable
Targets
technology
sectors: technology, aviation, telco · regions: middle-east
Sources cited
12
8 hosts
Action items (1)
Do-now tasks recorded on the entries about Microsoft Visual Studio, newest first. Check the date before acting on an older one.
- Install .NET 8.0.33, 9.0.22 or 10.0.14 (11 Release Candidate 3 for the preview) on every host that runs .NET applications, including Windows hosts already updated on 2026-10-13, which still carry CVE-2026-70197; rebuild and republish self-contained applications and rebuild container images from the updated .NET images, because a runtime update on the host does not change a bundled runtime; install the November 2026 Windows cumulative update of each branch (KB5131096, KB5131085, KB5131090, KB5131080, KB5131087, KB5132061 or KB5132059) on every Windows endpoint and server, because Microsoft's record now lists Windows as affected and CISA lists the flaw as exploited.2026-10-26CVE-2026-111497 +3
Defender insights
What each entry about Microsoft Visual Studio tells a defender to do, newest first.
Exposure · detection
Exposure · triage · detection
Story timeline
- 2026-10-26CVE-2026-111497 / CVE-2026-70197, Microsoft .NET: an out-of-band release fixes a Brotli decoder flaw and delivers the Windows sockets fix that the 13 October update did not contain, in 8.0.33, 9.0.22 and 10.0.14 (CVSS 3.1 8.1)
- 2026-10-07CL-STA-1178 (Blinder Tunnel): an Iranian-nexus recruitment lure delivers a Visual Studio project that runs code when it is opened, then hijacks the .NET AppDomainManager, disables ETW and takes tasking from GitHub
Hunting pivots
CVEs (exploited first)
Releases covered
Microsoft Visual Studio ×2
ATT&CK techniques (15 across 7 tactics)
15 techniques observed across 2 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)
- Initial AccessExploit Public-Facing Application
- ExecutionCommand and Scripting Interpreter: PowerShell · Trusted Developer Utilities Proxy Execution: MSBuild · Exploitation for Client Execution · User Execution: Malicious File · Hijack Execution Flow: DLL · Hijack Execution Flow: AppDomainManager
- PersistenceBoot or Logon Autostart Execution: Registry Run Keys / Startup Folder
- Privilege EscalationExploitation for Privilege Escalation · Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder
- StealthObfuscated Files or Information · Masquerading: Match Legitimate Resource Name or Location · Trusted Developer Utilities Proxy Execution: MSBuild · Hijack Execution Flow: DLL · Hijack Execution Flow: AppDomainManager
- Defense ImpairmentDisable or Modify Tools
- Command and ControlWeb Service: Dead Drop Resolver · Web Service: Bidirectional Communication · Protocol Tunneling
Initial Access TA0001
T1190Exploit Public-Facing Application×1
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
Evidence: 2026-10-26/cve-2026-111497-microsoft-net-oob-update-brotli-sockets-fix · ATT&CK page ↗
Execution TA0002
T1059.001Command and Scripting Interpreter: PowerShell×1
Adversaries may abuse PowerShell commands and scripts for execution. PowerShell is a powerful interactive command-line interface and scripting environment included in the Windows operating system. PowerShell can also be installed on Linux and macOS. Adversaries can use PowerShell to perform a number of actions, including discovery of information and execution of code. Examples include the <code>Start-Process</code> cmdlet which can be used to run an executable and the <code>Invoke-Command</code> cmdlet which runs a command locally or on a remote computer (though administrator permissions are required to use PowerShell to connect to remote systems).
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1127.001Trusted Developer Utilities Proxy Execution: MSBuild×1
Adversaries may use MSBuild to proxy execution of code through a trusted Windows utility. MSBuild.exe (Microsoft Build Engine) is a software build platform used by Visual Studio. It handles XML formatted project files that define requirements for loading and building various platforms and configurations.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1203Exploitation for Client Execution×1
Adversaries may exploit software vulnerabilities in client applications to execute code. Vulnerabilities can exist in software due to unsecure coding practices that can lead to unanticipated behavior. Adversaries can take advantage of certain vulnerabilities through targeted exploitation for the purpose of arbitrary code execution. Oftentimes the most valuable exploits to an offensive toolkit are those that can be used to obtain code execution on a remote system because they can be used to gain access to that system. Users will expect to see files related to the applications they commonly used to do work, so they are a useful target for exploit research and development because of their high utility.
Evidence: 2026-10-26/cve-2026-111497-microsoft-net-oob-update-brotli-sockets-fix · ATT&CK page ↗
T1204.002User Execution: Malicious File×1
An adversary may rely upon a user opening a malicious file in order to gain execution. Users may be subjected to social engineering to get them to open a file that will lead to code execution. This user action will typically be observed as follow-on behavior from Spearphishing Attachment. Adversaries may use several types of files that require a user to execute them, including .doc, .pdf, .xls, .rtf, .scr, .exe, .lnk, .pif, .cpl, .reg, and .iso.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1574.001Hijack Execution Flow: DLL×1
Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses. DLLs are libraries that contain code and data that can be simultaneously utilized by multiple programs. While DLLs are not malicious by nature, they can be abused through mechanisms such as side-loading, hijacking search order, and phantom DLL hijacking.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1574.014Hijack Execution Flow: AppDomainManager×1
Adversaries may execute their own malicious payloads by hijacking how the .NET `AppDomainManager` loads assemblies. The .NET framework uses the `AppDomainManager` class to create and manage one or more isolated runtime environments (called application domains) inside a process to host the execution of .NET applications. Assemblies (`.exe` or `.dll` binaries compiled to run as .NET code) may be loaded into an application domain as executable code.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Persistence TA0003
T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Privilege Escalation TA0004
T1068Exploitation for Privilege Escalation×1
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.
Evidence: 2026-10-26/cve-2026-111497-microsoft-net-oob-update-brotli-sockets-fix · ATT&CK page ↗
T1547.001Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder×1
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Stealth TA0005
T1027Obfuscated Files or Information×1
Adversaries may attempt to make an executable or file difficult to discover or analyze by encrypting, encoding, or otherwise obfuscating its contents on the system or in transit. This is common behavior that can be used across different platforms and the network to evade defenses.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1036.005Masquerading: Match Legitimate Resource Name or Location×1
Adversaries may match or approximate the name or location of legitimate files, Registry keys, or other resources when naming/placing them. This is done for the sake of evading defenses and observation.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1127.001Trusted Developer Utilities Proxy Execution: MSBuild×1
Adversaries may use MSBuild to proxy execution of code through a trusted Windows utility. MSBuild.exe (Microsoft Build Engine) is a software build platform used by Visual Studio. It handles XML formatted project files that define requirements for loading and building various platforms and configurations.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1574.001Hijack Execution Flow: DLL×1
Adversaries may abuse dynamic-link library files (DLLs) in order to achieve persistence, escalate privileges, and evade defenses. DLLs are libraries that contain code and data that can be simultaneously utilized by multiple programs. While DLLs are not malicious by nature, they can be abused through mechanisms such as side-loading, hijacking search order, and phantom DLL hijacking.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1574.014Hijack Execution Flow: AppDomainManager×1
Adversaries may execute their own malicious payloads by hijacking how the .NET `AppDomainManager` loads assemblies. The .NET framework uses the `AppDomainManager` class to create and manage one or more isolated runtime environments (called application domains) inside a process to host the execution of .NET applications. Assemblies (`.exe` or `.dll` binaries compiled to run as .NET code) may be loaded into an application domain as executable code.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Defense Impairment TA0112
T1685Disable or Modify Tools×1
Adversaries may disable, degrade, or tamper with security tools or applications (e.g., endpoint detection and response (EDR) tools, intrusion detection systems (IDS), antivirus, logging agents, sensors, etc.) to impair or reduce visibility of defensive capabilities. This may include stopping specific services, killing processes, modifying or deleting tool configuration files and Registry keys, or preventing tools from updating. This may also include impairing defenses more broadly by disrupting preventative, detection, and response mechanisms across host, network, and cloud environments.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Command and Control TA0011
T1102.001Web Service: Dead Drop Resolver×1
Adversaries may use an existing, legitimate external Web service to host information that points to additional command and control (C2) infrastructure. Adversaries may post content, known as a dead drop resolver, on Web services with embedded (and often obfuscated/encoded) domains or IP addresses. Once infected, victims will reach out to and be redirected by these resolvers.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1102.002Web Service: Bidirectional Communication×1
Adversaries may use an existing, legitimate external Web service as a means for sending commands to and receiving output from a compromised system over the Web service channel. Compromised systems may leverage popular websites and social media to host command and control (C2) instructions. Those infected systems can then send the output from those commands back over that Web service channel. The return traffic may occur in a variety of ways, depending on the Web service being utilized. For example, the return traffic may take the form of the compromised system posting a comment on a forum, issuing a pull request to development project, updating a document hosted on a Web service, or by sending a Tweet.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
T1572Protocol Tunneling×1
Adversaries may tunnel network communications to and from a victim system within a separate protocol to avoid detection/network filtering and/or enable access to otherwise unreachable systems. Tunneling involves explicitly encapsulating a protocol within another. This behavior may conceal malicious traffic by blending in with existing traffic and/or provide an outer layer of encryption (similar to a VPN). Tunneling could also enable routing of network packets that would otherwise not reach their intended destination, such as SMB, RDP, or other traffic that would be filtered by network appliances or not routed over the Internet.
Evidence: 2026-10-07/cl-sta-1178-blinder-tunnel-csproj-lure-github-c2 · ATT&CK page ↗
Entries about Microsoft Visual Studio (2)
Co-occurring entities
Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.
- .NET and Visual Studio System.Net.Sockets memory corruption on Windows (SocketAsyncEventArgs reuse across IPv4 and IPv6 datagram sockets, CVSS 3.1 8.1): the 2026-10-13 release did not contain the fix, corrected in .NET 8.0.33, 9.0.22 and 10.0.14 on 2026-10-25×1
- ASP.NET Core and source-built .NET Linux tarballs with incorrect file ownership (local privilege escalation, CVSS 3.1 7.8), fixed in .NET 8.0.33, 9.0.22, 10.0.14 on 2026-10-25×1
- ASP.NET Core Blazor WebAssembly debugger code execution (CVSS 3.1 8.8, user interaction): the 2026-10-13 release did not fully address it; standalone Server and DevServer packages 10.0.14 and 11.0.0-rc.3 carry the fix×1
- Blackwood×1
- Blinder Tunnel×1
- CL-STA-1178×1
- Google Brotli×1
- Microsoft .NET×1
Where this entity is cited
Source distribution
- github.com4 (33%)
- msrc.microsoft.com2 (17%)
- cisa.gov1 (8%)
- devblogs.microsoft.com1 (8%)
- ellio.tech1 (8%)
- nodejs.org1 (8%)
- research.jfrog.com1 (8%)
- unit42.paloaltonetworks.com1 (8%)
All cited sources (12)
- cisa.govCISA (alert, KEV additions)https://www.cisa.gov/news-events/alerts/2026/10/27/cisa-adds-two-known-exploited-vulnerabilities-catalog
- devblogs.microsoft.com.NET Blog (Microsoft)https://devblogs.microsoft.com/dotnet/dotnet-october-2026-oob-security-updates/
- ellio.techELLIO Threat Research Labhttps://ellio.tech/en/blog/node2shell-cve-2026-111497-rce-on-stock-nodejs-builds/
- github.comMicrosoft (dotnet/announcements, CVE-2026-102870 advisory)https://github.com/dotnet/announcements/issues/492
- github.comMicrosoft (dotnet/announcements, CVE-2026-111497 advisory)https://github.com/dotnet/announcements/issues/494
- github.comMicrosoft (dotnet/announcements, CVE-2026-114148 advisory)https://github.com/dotnet/announcements/issues/495
- github.comMicrosoft (dotnet/runtime, CVE-2026-70197 advisory)https://github.com/dotnet/runtime/issues/136445
- msrc.microsoft.comMicrosoft Security Response Center (CVE-2026-111497)https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-111497
- msrc.microsoft.comMicrosoft Security Response Center (CVE-2026-70197)https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70197
- nodejs.orgNode.js projecthttps://nodejs.org/en/blog/vulnerability/october-2026-security-releases
- research.jfrog.comJFrog Security Researchhttps://research.jfrog.com/post/brotli2shell-beyond-node2shell-and-http2shell/
- unit42.paloaltonetworks.comPalo Alto Networks Unit 42https://unit42.paloaltonetworks.com/blinder-tunnel-targets-critical-infrastructure/