Microsoft patches three high-severity vulnerabilities in .NET Aspire CLI

Microsoft disclosed and fixed three high-severity vulnerabilities in its .NET Aspire CLI and Hosting stack on November 10, 2026, publishing the first advisory as Aspire Information Disclosure Vulnerability (CVE-2026-120792) on the GitHub Advisory Database. The issues cover an information-disclosure bug in the Aspire CLI's deprecated MCP-config scanner, a local privilege-escalation flaw tied to insecure temp-directory permissions during MSBuild operations, and a Dashboard credential-replay bug exploitable through a malicious container. All three are fixed in version 13.6.5.

What changed

• CVE-2026-120792 (CVSS 7.3, CWE-532): the Aspire CLI's deprecated MCP configuration scanner writes config content to a fixed, shared temp-directory path on Linux and macOS, exposing it to other local users
• CVE-2026-120778 (CVSS 7.3, CWE-379): insecure temp-directory permissions let a local attacker plant files picked up by MSBuild response-file discovery during aspire sdk generate/dump/export, executing code as the developer on Linux (x64, arm64, musl-x64) and macOS (x64, arm64) builds
• CVE-2026-120006 (CVSS 7.5): Dashboard authentication credentials can be replayed by an attacker-controlled container, letting it execute code as the host developer on macOS setups with a Dashboard-authenticated AppHost and a linked HTTPS YARP gateway
• Affected packages: Aspire.Cli (NuGet) 13.2.0 to 13.6.4, @microsoft/aspire-cli (npm) 13.4.2 to 13.6.4, and Aspire.Hosting/Aspire.Hosting.AppHost versions before 13.6.5
• All three vulnerabilities are fixed in version 13.6.5, released across both the NuGet and npm distributions

What it means for builders

.NET Aspire is Microsoft's cloud-native developer stack with built-in MCP tooling, so the flaws matter most in shared environments. An attacker with access to a shared development machine, a CI runner, or a malicious container could escalate to a developer's own privileges or read MCP server configuration data that was never meant to leave the local machine.

Advisories and what to do

Microsoft published two further advisories alongside the fix: Aspire Elevation of Privilege Vulnerability (CVE-2026-120778) and Aspire Elevation of Privilege Vulnerability (CVE-2026-120006), both dated November 10, 2026. Teams running Aspire CLI or Hosting packages on shared machines or CI runners should upgrade to version 13.6.5 to close all three issues.

Sources

• Aspire Information Disclosure Vulnerability (CVE-2026-120792) (GitHub Advisory Database / Microsoft, November 10, 2026, official)
• Aspire Elevation of Privilege Vulnerability (CVE-2026-120778) (GitHub Advisory Database / Microsoft, November 10, 2026, official)
• Aspire Elevation of Privilege Vulnerability (CVE-2026-120006) (GitHub Advisory Database / Microsoft, November 10, 2026, official)

Written with AI assistance, strictly from the sources listed above. Before it went live, automated checks verified its dates, sources and every language edition.