Loading
Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 13.2.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.3.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.3.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.3.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.3.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.3.0, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Vulnerable: >= 13.4.2, < 13.6.5
Patched in 13.6.5
Details
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.
Insecure temporary files used by Aspire CLI can allow a local attacker to obtain sensitive configuration information.
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/518
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:L| Package | Affected version | Patched version |
|---|---|---|
| Aspire CLI (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 |
| 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 component is the Aspire CLI's deprecated MCP configuration scanner, which ships in the CLI packages listed above. Its temporary-file diagnostics can include configuration content and use a fixed path in a shared temporary directory.
The reported scenario involves running Aspire CLI agent or MCP initialization commands on a non-Windows system with a temporary directory shared by multiple users. 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.
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.
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.
You can ask questions about this issue in the Aspire repository.
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.
V1.0 (November 10, 2026): Advisory published.
More nuget advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.