Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-m63f-xhvm-6mv5
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in the Aspire CLI. This advisory provides guidance on updating affected applications and components.
An insecure temporary directory used by Aspire CLI-generated builds can allow a local attacker to influence MSBuild response-file discovery and execute code with the privileges of the developer running the CLI.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/519
CVSS Details
- Version: 3.1
- Severity: High
- Score: 7.3
- Vector:
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H - Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)
- MSRC severity: Important
Affected Platforms
- Platforms: Linux, macOS
- Architectures: x64, Arm64
<a name="affected-packages"></a>Affected Packages
Standalone Aspire CLI
Package | Affected version | Patched version --- | --- | --- Aspire.Cli | >= 13.2.0, < 13.6.5 | 13.6.5 Aspire.Cli.linux-x64 | >= 13.3.0, < 13.6.5 | 13.6.5 Aspire.Cli.linux-arm64 | >= 13.3.0, < 13.6.5 | 13.6.5 Aspire.Cli.linux-musl-x64 | >= 13.3.0, < 13.6.5 | 13.6.5 Aspire.Cli.osx-x64 | >= 13.3.0, < 13.6.5 | 13.6.5 Aspire.Cli.osx-arm64 | >= 13.3.0, < 13.6.5 | 13.6.5
Aspire CLI npm packages
Package | Affected version | Patched version --- | --- | --- @microsoft/aspire-cli | >= 13.4.2, < 13.6.5 | 13.6.5 @microsoft/aspire-cli-linux-x64 | >= 13.4.2, < 13.6.5 | 13.6.5 @microsoft/aspire-cli-linux-arm64 | >= 13.4.2, < 13.6.5 | 13.6.5 @microsoft/aspire-cli-linux-musl-x64 | >= 13.4.2, < 13.6.5 | 13.6.5 @microsoft/aspire-cli-osx-x64 | >= 13.4.2, < 13.6.5 | 13.6.5 @microsoft/aspire-cli-osx-arm64 | >= 13.4.2, < 13.6.5 | 13.6.5
The affected scenario concerns CLI-generated server and integration builds on non-Windows systems when a local attacker can influence automatic MSBuild response-file discovery through an attacker-writable directory. This includes builds started by aspire sdk generate, aspire sdk dump, and aspire sdk export.
Advisory FAQ
<a name="how-affected"></a>How do I know if I am affected?
The reported scenario involves a local attacker influencing a generated build through a shared temporary-directory ancestor while another user invokes the Aspire CLI. Versions 13.2.0 through 13.6.4 are affected.
Aspire ships independently of .NET. Installing a .NET runtime or SDK update does not establish that the affected Aspire CLI has been updated.
<a name="how-fix"></a>How do I fix the issue?
Update the Aspire CLI to version 13.6.5 or later. If installed as a .NET tool, update the Aspire.Cli package. If installed using npm, update @microsoft/aspire-cli to version 13.6.5 or later; its platform-specific dependency must also resolve to version 13.6.5 or later. Otherwise update the CLI through its installation method.
Other Information
Reporting Security Issues
If you have found a potential security issue in a supported version of .NET, please report it to the Microsoft Security Response Center (MSRC) via the MSRC Researcher Portal. Further information can be found in the MSRC Report an Issue FAQ.
Security reports made through MSRC may qualify for the Microsoft .NET Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.
Support
You can ask questions about this issue in the Aspire repository.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
External Links
Acknowledgements
- l8BL with ENKI WhiteHat
Revisions
V1.0 (November 10, 2026): Advisory published.
Upload your own SBOM in CycloneDX 1.6 or higher (JSON) directly here to check your vulnerabilities.
Drag and drop some file here, or click to select
The vulnerability requires local access to the device to be exploited. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. The attacker needs the user to perform some action, like clicking a link. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
Probability that this vulnerability will be exploited in the wild within the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
- EUVD-2026-122467Alias
- CVE-2026-120778Alias
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard