Shared Aspire CLI temp files expose configuration to local users
A local user on shared Linux or macOS hardware can read sensitive Aspire CLI configuration because the tool writes diagnostics to a fixed temporary-file path, Microsoft's advisory says. Microsoft attributes the flaw to the CLI's deprecated MCP configuration scanner.
- Affected
- Aspire.Cli (nuget) >= 13.2.0, < 13.6.5; Aspire.Cli.linux-x64/arm64/musl-x64 and osx-x64/arm64 >= 13.3.0, < 13.6.5; @microsoft/aspire-cli and npm platform packages >= 13.4.2, < 13.6.5
- Fixed
- 13.6.5 for all affected packages
The report's scenario is a non-Windows host whose temporary directory is shared by multiple users, with agent or MCP initialization commands running. Microsoft rates it High at CVSS 7.3, with local access, low complexity, and an information-disclosure impact on Linux and macOS, x64 and Arm64. Installing a .NET runtime or SDK update does not by itself update the independently shipped Aspire CLI.
Affected releases include NuGet Aspire.Cli 13.2.0 to below 13.6.5, NuGet platform packages from 13.3.0, and npm @microsoft/aspire-cli and its platform packages from 13.4.2; all are fixed at 13.6.5. Users should update the CLI to version 13.6.5 or later, and npm installs must also resolve platform-specific dependencies to 13.6.5 or later.
Sources & technical scope 1 source
GitHub Advisory Database — original source ↗
Affected: Aspire.Cli (nuget) >= 13.2.0, < 13.6.5; Aspire.Cli.linux-x64/arm64/musl-x64 and osx-x64/arm64 >= 13.3.0, < 13.6.5; @microsoft/aspire-cli and npm platform packages >= 13.4.2, < 13.6.5
Fixed: 13.6.5 for all affected packages
Exploitation: Local exploitation is possible in the described shared-temp-directory scenario; supplied evidence does not show active exploitation or a KEV listing.
Scope & limitations: Supplied evidence does not establish individually tested versions, exploitation in the wild, or impact on Windows; affected platforms are listed as Linux and macOS.
External findings belong to the credited researchers.