CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

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.

2026-10-26NOTABLEexploitedMicrosoft ships out-of-band .NET fixes: hosts updated on 13 October still carry the Windows sockets flaw

Exposure · detection

2026-10-07NOTABLEUnit 42: a coding-test Visual Studio project executes on open, then disables ETW and takes tasking from GitHub

Exposure · triage · detection

Story timeline

  1. 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)
    trending-vulnerabilitiesMicrosoft ships out-of-band .NET fixes: hosts updated on 13 October still carry the Windows sockets flaw
  2. 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
    active-threatsUnit 42: a coding-test Visual Studio project executes on open, then disables ETW and takes tasking from GitHub
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)

2026-10-26 · view entry permalink →

NOTABLECVE-2026-111497 +3exploitedupdatedNATOA2

CVE-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)

Microsoft released out-of-band security updates for .NET 8, .NET 9 and .NET 10, with .NET 11 Release Candidate 3, on 2026-10-25 (.NET Blog, 2026-10-25). .NET Framework is not affected (.NET Blog, 2026-10-25). CVE-2026-111497 is a buffer overflow in the Brotli decoder that .NET uses and may let an unauthenticated attacker read or corrupt process memory, leading to information disclosure, denial of service or elevation of privilege (.NET Blog, 2026-10-25); Microsoft scores it CVSS 3.1 8.1, marked it publicly disclosed and not exploited on 2026-10-25, and rates it Exploitation More Likely (MSRC, 2026-10-25). Node.js fixed the same CVE on 2026-10-21 (Node.js project, 2026-10-21). Microsoft says an application is exposed only if it decompresses attacker-controlled Brotli data through ASP.NET Core request decompression, HttpClient automatic response decompression that includes Brotli, or the BrotliStream and BrotliDecoder APIs, and that ASP.NET Core and HttpClient do not decompress Brotli by default (dotnet/announcements #494, 2026-10-25).

The release also corrects two fixes of 2026-10-13: Microsoft says that release did not fully address CVE-2026-70197 and CVE-2026-102870 (.NET Blog, 2026-10-25). CVE-2026-70197 is a Windows-only out-of-bounds write: reusing one SocketAsyncEventArgs instance across IPv4 and IPv6 datagram sockets can keep an undersized cached native address buffer, and an unauthenticated attacker can then write out of bounds during ReceiveFromAsync (CVSS 3.1 8.1, high attack complexity) (dotnet/runtime #136445, 2026-10-25); the Security Update Guide rates it not exploited, not publicly disclosed and Exploitation Less Likely (MSRC, 2026-10-25). CVE-2026-102870 is code execution in the Blazor WebAssembly debugger when a developer evaluates an expression that involves attacker-controlled application data (CVSS 3.1 8.8, user interaction required); it needs the standalone Server and DevServer package references updated, because updating only the shared runtime is not a substitute (dotnet/announcements #492, 2026-10-25). CVE-2026-114148 is a local privilege escalation through incorrect file ownership in Linux tarballs (CVSS 3.1 7.8), affecting ASP.NET Core tarballs of .NET 8 and 9 and source-built tarballs of .NET 8 to 11 (dotnet/announcements #495, 2026-10-25). No source reports an attack on .NET, but CISA lists CVE-2026-111497 as exploited since 2026-10-27 (CISA, 2026-10-27).

Today, we are releasing out-of-band (OOB) security updates for .NET 8, .NET 9, and .NET 10, along with .NET 11 Release Candidate 3.

because the October 13, 2026 release did not fully address these issues

.NET Blog (Microsoft) 2026-10-25

ASP.NET Core and HttpClient do not automatically decompress Brotli data in their default configurations.

Microsoft (dotnet/announcements, CVE-2026-111497 advisory) 2026-10-25

based on evidence of active exploitation

CISA (alert, KEV additions) 2026-10-27

Updated the Security Updates table to include affected Windows versions and the applicable November 2026 security updates.

Microsoft Security Response Center (record revision 7) 2026-11-12
Updaterun 2026-10-28T0256Z-intelsummarytagscvessourcesevidencesourcing_notebody

CISA added CVE-2026-111497, the Brotli decoder flaw this release fixes for .NET, to its Known Exploited Vulnerabilities catalog on 2026-10-27 "based on evidence of active exploitation", without describing the evidence (CISA, 2026-10-27). ELLIO's sensors recorded exploit traffic against Node.js 24.22.0 on 2026-10-26 (ELLIO, 2026-10-26); no source reports an attack on .NET, and Microsoft's own record marked the flaw not exploited on 2026-10-25 (MSRC, 2026-10-25).

Correctionrun 2026-11-01T1312Z-auditbodycvessources

For CVE-2026-114148, the incorrect file ownership in Linux tarballs, Microsoft's advisory names the fixed packages as the ASP.NET Core 8 and 9 runtime and targeting-pack tarballs 8.0.33 and 9.0.22 and, for source-built Linux distributions, SDK releases 8.0.133, 9.0.123, 10.0.114, 10.0.403 and 11.0.100-rc.3; it lists no 10.0.14 or 11.0.0-rc.3 fix for this flaw (dotnet/announcements #495, 2026-10-25). JFrog reproduced a .NET runtime crash through Brotli decompression, the process-crash signal the Detection line names (JFrog, 2026-10-25).

Updaterun 2026-11-13T0256Z-intelsummarycvesactionssourcesevidencesourcing_notebodyaffected_products

Microsoft's record for CVE-2026-111497, revised on 2026-11-12, now lists Windows as affected: the revision note says it updated the Security Updates table to include affected Windows versions and the applicable November 2026 security updates (Microsoft Security Response Center, 2026-11-12). The fixes are the November 2026 cumulative updates, KB5131096 for Windows 10 21H2 and 22H2, KB5131085 for Windows 10 1809 and Server 2019, KB5131090 for Server 2022, KB5131080, or the earlier KB5131077, for Server 2025, KB5131087 for Windows 11 23H2, KB5132061, or the earlier KB5132043, for Windows 11 24H2, 25H2 and 26H2 and KB5132059 for Windows 11 26H1, and the record still marks the flaw not exploited although CISA lists it (Microsoft Security Response Center, 2026-11-12). The record names no Windows component, and it also lists PowerShell 7.4 to 7.6 and Visual Studio 2017 to 2026 as affected (Microsoft Security Response Center, 2026-11-12).

Builds on: Node2Shell Brotli flaw is now on CISA KEV, with exploit traffic seen against Node.js 24.22.0…

vulnerability26 Oct 03:36Zsingle-sourceOpen finding →

2026-10-07 · view entry permalink →

NOTABLENATOB2

CL-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

Unit 42 tracks an Iranian state-aligned cluster as CL-STA-1178 and names its March 2026 campaign against an individual in Iraqi critical infrastructure "Blinder Tunnel"; the infrastructure was staged from November 2025, and the same actor ran conflict-themed Google Drive credential phishing against an Israeli entity in May and June 2026 (Unit 42, 2026-10-06). A recruiter persona impersonating the Dubai Airports IT department sent a decoy career-portal installer and then a weaponised C# Visual Studio project as an at-home coding test (Unit 42, 2026-10-06). When a developer opens a project, Visual Studio runs a design-time build in the background, and the project file overrides one of the targets that step runs, so the payload executes at project load, before any compile; it copies binaries into a folder under the user profile and launches one of them (Unit 42, 2026-10-06).

The launched binary is a renamed, signed Microsoft Visual Studio hosting process. A configuration file beside it replaces the .NET application's default app-domain manager with a malicious one and sets the ETW enable flag to false, which Unit 42 says could impair detection, and the loader, ShelbyLoader V2, then arrives through DLL sideloading (Unit 42, 2026-10-06). The loader persists through a current-user startup registry value, authenticates to the GitHub API with a hard-coded personal access token for tasking, and falls back to encrypted routing data in comments on GitHub issues; a follow-on module hooks the PowerShell engine inside the hijacked process, so commands run without starting powershell.exe, and a second loader, Blackwood, runs the open-source Chisel tunnelling tool in memory to give a reverse SOCKS proxy into the victim's network (Unit 42, 2026-10-06). GitHub removed the malicious infrastructure Unit 42 identified, and Unit 42 is not aware of any breach of Dubai Airports (Unit 42, 2026-10-06).

Triage: developers legitimately build projects and call GitHub, so the discriminators are that execution starts at project open rather than at a build the developer chose to run, a DLL beside a renamed signed host binary that does not belong to it, and a configuration file that changes ETW or app-domain settings.

We discovered that an Iranian state-aligned threat actor has been masquerading as the Dubai Airports IT department to deliver trojanized coding challenges to high-value targets.

the attackers defined a custom XML target with this exact name in their malicious .csproj file, overriding the safe Microsoft default behavior.

Because Event Tracing for Windows (ETW) is critical for monitoring execution and detecting in-memory threats, this flag could impair detection capabilities.

This allowed the attacker's script to execute without spawning PowerShell.exe.

Palo Alto Networks Unit 42 2026-10-06
threat07 Oct 04:47Zsingle-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats1
  • Vulns1

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)