An insecure temporary directory can let a local attacker influence MSBuild response-file discovery.The attacker needs local access and low privileges. A developer must then run an affected CLI-generated build, which can execute attacker-influenced code with that developer's privileges.
What it allows
How Does CVE-2026-120778 Elevate Privileges?
Aspire CLI-generated server and integration builds use a temporary-directory path on non-Windows systems. Microsoft says an attacker-writable directory can influence automatic MSBuild response-file discovery.
The affected scenario includes builds started by the Aspire SDK generate, dump, and export operations. This profile omits command syntax and response-file details because defenders do not need them to remediate the flaw.
The attacker must already have local, low-privilege access to a system with an affected Aspire CLI. Another user must invoke the generated build, satisfying the CVSS requirement for user interaction.
If successful, attacker-influenced code runs with the developer's privileges. Microsoft's vector rates potential confidentiality, integrity, and availability impacts as high, while scope remains unchanged.
What Is Known About CVE-2026-120778 Exploitation?
CVE-2026-120778 was not listed in CISA's Known Exploited Vulnerabilities catalog version 2026.11.10. This dated catalog status does not prove that exploitation has not occurred.
Who is affected
Which Aspire CLI Versions Are Affected by CVE-2026-120778?
The standalone Aspire.Cli package is affected from 13.2.0 through 13.6.4. Its Linux and macOS architecture packages are affected from 13.3.0 through 13.6.4.
The @microsoft/aspire-cli npm package and its Linux and macOS platform packages are affected from 13.4.2 through 13.6.4. Microsoft lists x64, Arm64, and Linux musl x64 packages where applicable.
Version 13.6.5 fixes every package listed in the advisory. Windows is not listed as an affected platform, and installing a .NET runtime or SDK update does not confirm that Aspire CLI was updated.
Teams should track the upgrade through their vulnerability management process. They should verify the CLI package and its platform-specific dependency independently.
Timeline
- 2026-11-10
Microsoft published the Aspire CLI advisory and released version 13.6.5 as the patched version.
- 2026-11-11
GitHub reviewed and updated GHSA-m63f-xhvm-6mv5 for CVE-2026-120778.
What to do
-
Inventory Aspire CLI installations
Identify standalone, .NET tool, and npm installations on Linux and macOS. Record each CLI package and its platform-specific dependency version.
-
Upgrade every listed package to 13.6.5 or later
Use the installation method that deployed Aspire CLI. Confirm both the main package and any platform-specific package resolve to version 13.6.5 or later.
-
Prioritize shared development systems
Prioritize systems where multiple local users can access a shared temporary-directory ancestor. The vendor's affected scenario depends on local access and another user's build invocation.
-
Review affected build activity
Review Aspire CLI-generated server and integration build activity for unexpected privilege use or code execution. Preserve relevant evidence and follow the incident response plan when anomalies appear.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-120778 in Brandefense Atlas
The Atlas record of CVE-2026-120778: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
What is CVE-2026-120778?
It is a high-severity Aspire CLI privilege escalation flaw. An insecure temporary directory can let a local attacker influence MSBuild response-file discovery.
Which platforms are affected by CVE-2026-120778?
Microsoft lists Linux and macOS on x64 and Arm64, plus a Linux musl x64 package. Windows is not listed as affected.
Which Aspire CLI version fixes CVE-2026-120778?
Microsoft lists Aspire CLI 13.6.5 as the patched version for every affected standalone, .NET tool, and npm package in its advisory.
Does updating the .NET SDK fix CVE-2026-120778?
Not by itself. Microsoft says Aspire ships independently, so a .NET runtime or SDK update does not establish that Aspire CLI was updated.
What access does exploitation require?
Microsoft's CVSS vector requires local access, low privileges, and user interaction. The scenario also requires influence over a shared temporary-directory ancestor.
Sources
- Microsoft Security Advisory CVE-2026-120778GitHub Advisory Database
- CVE-2026-120778Microsoft Security Response Center
- NVD: CVE-2026-120778National Institute of Standards and Technology
- Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency