Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Aspire Elevation of Privilege Vulnerability

CVSS 3.1 7.3 HIGHEUVD CVSS 3.1 7.3 CVSS 3.1 · [email protected] · Primary 7.3 HIGHCVSS_V3 Publisher rating HIGHFixed by Aspire.Cli 13.6.5Fixed by Aspire.Cli.linux-x64 13.6.5Fixed by Aspire.Cli.linux-arm64 13.6.5Fixed by Aspire.Cli.linux-musl-x64 13.6.5KEV status unknown

cve-program · CVE-2026-120778

Published

Creation of temporary file in directory with insecure permissions in .NET Aspire allows an authorized attacker to elevate privileges locally.

Read the publisher's advisory

euvd · EUVD-2026-122467

Published

Creation of temporary file in directory with insecure permissions in .NET Aspire allows an authorized attacker to elevate privileges locally.

Read the publisher's advisory

nvd · CVE-2026-120778

Published

Creation of temporary file in directory with insecure permissions in .NET Aspire allows an authorized attacker to elevate privileges locally.

Read the publisher's advisory

osv · GHSA-m63f-xhvm-6mv5

Published

## 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](https://www.nuget.org/packages/Aspire.Cli) | >= 13.2.0, < 13.6.5 | 13.6.5 [Aspire.Cli.linux-x64](https://www.nuget.org/packages/Aspire.Cli.linux-x64) | >= 13.3.0, < 13.6.5 | 13.6.5 [Aspire.Cli.linux-arm64](https://www.nuget.org/packages/Aspire.Cli.linux-arm64) | >= 13.3.0, < 13.6.5 | 13.6.5 [Aspire.Cli.linux-musl-x64](https://www.nuget.org/packages/Aspire.Cli.linux-musl-x64) | >= 13.3.0, < 13.6.5 | 13.6.5 [Aspire.Cli.osx-x64](https://www.nuget.org/packages/Aspire.Cli.osx-x64) | >= 13.3.0, < 13.6.5 | 13.6.5 [Aspire.Cli.osx-arm64](https://www.nuget.org/packages/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](https://www.npmjs.com/package/@microsoft/aspire-cli) | >= 13.4.2, < 13.6.5 | 13.6.5 [@microsoft/aspire-cli-linux-x64](https://www.npmjs.com/package/@microsoft/aspire-cli-linux-x64) | >= 13.4.2, < 13.6.5 | 13.6.5 [@microsoft/aspire-cli-linux-arm64](https://www.npmjs.com/package/@microsoft/aspire-cli-linux-arm64) | >= 13.4.2, < 13.6.5 | 13.6.5 [@microsoft/aspire-cli-linux-musl-x64](https://www.npmjs.com/package/@microsoft/aspire-cli-linux-musl-x64) | >= 13.4.2, < 13.6.5 | 13.6.5 [@microsoft/aspire-cli-osx-x64](https://www.npmjs.com/package/@microsoft/aspire-cli-osx-x64) | >= 13.4.2, < 13.6.5 | 13.6.5 [@microsoft/aspire-cli-osx-arm64](https://www.npmjs.com/package/@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](https://msrc.microsoft.com/report/vulnerability/new). Further information can be found in the MSRC [Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue). 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](https://github.com/microsoft/aspire). ### 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 [CVE-2026-120778](https://www.cve.org/CVERecord?id=CVE-2026-120778) ### Acknowledgements - l8BL with [ENKI WhiteHat](https://enki.co.kr/) ### Revisions V1.0 (November 10, 2026): Advisory published.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2026-120778

Published

Aspire.Cli

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "Microsoft",
                    "product": "Aspire.Cli",
                    "platforms": [
                        "Linux",
                        "Mac OS"
                    ],
                    "versions": [
                        {
                            "version": "13.5.4",
                            "lessThan": "13.6.5",
                            "versionType": "custom",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2026-122467

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Nov 10, 2026, 6:23:52 PM

dateUpdated: Nov 16, 2026, 7:28:56 PM

1 related source bulletins · separate from aliases

NCSC-2026-0473: Kwetsbaarheden verholpen in Microsoft Developer Tools

CVE-2026-70094 · CVE-2026-70175 · CVE-2026-85923 · CVE-2026-102230 · CVE-2026-102236 · CVE-2026-105544 · CVE-2026-109467 · CVE-2026-109475 · CVE-2026-109476 · CVE-2026-109478 · CVE-2026-109481 · CVE-2026-112745 · CVE-2026-114146 · CVE-2026-114147 · CVE-2026-114149 · CVE-2026-114150 · CVE-2026-114151 · CVE-2026-114152 · CVE-2026-114154 · CVE-2026-114155 · CVE-2026-114156 · CVE-2026-114157 · CVE-2026-114158 · CVE-2026-114159 · CVE-2026-114171 · CVE-2026-118741 · CVE-2026-118745 · CVE-2026-118746 · CVE-2026-118747 · CVE-2026-118748 · CVE-2026-118749 · CVE-2026-118750 · CVE-2026-119975 · CVE-2026-119976 · CVE-2026-119981 · CVE-2026-119982 · CVE-2026-119983 · CVE-2026-119985 · CVE-2026-120778 · CVE-2026-120779 · CVE-2026-120780 · CVE-2026-120782 · CVE-2026-120796 · CVE-2026-121660 · CVE-2026-121661 · CVE-2026-121662 · CVE-2026-121663 · CVE-2026-121664 · CVE-2026-121665

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2026-120778

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Awaiting Analysis

Weakness classifications: CWE-379

Original publisher date fields

published: 2026-11-10T19:20:26.887

lastModified: 2026-11-10T19:20:27.010

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-m63f-xhvm-6mv5

Published

Aspire.Cli

NuGet

ECOSYSTEM · introduced 13.2.0 → fixed 13.6.5

28 versions listed as affected

13.2.0, 13.2.1, 13.2.2, 13.2.3, 13.2.4, 13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

Aspire.Cli.linux-x64

NuGet

ECOSYSTEM · introduced 13.3.0 → fixed 13.6.5

23 versions listed as affected

13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

Aspire.Cli.linux-arm64

NuGet

ECOSYSTEM · introduced 13.3.0 → fixed 13.6.5

23 versions listed as affected

13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

Aspire.Cli.linux-musl-x64

NuGet

ECOSYSTEM · introduced 13.3.0 → fixed 13.6.5

23 versions listed as affected

13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

Aspire.Cli.osx-x64

NuGet

ECOSYSTEM · introduced 13.3.0 → fixed 13.6.5

23 versions listed as affected

13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

Aspire.Cli.osx-arm64

NuGet

ECOSYSTEM · introduced 13.3.0 → fixed 13.6.5

23 versions listed as affected

13.3.0, 13.3.1, 13.3.2, 13.3.3, 13.3.4, 13.3.5, 13.4.0, 13.4.1, 13.4.2, 13.4.3, 13.4.4, 13.4.5, 13.4.6, 13.5.0, 13.5.1, 13.5.2, 13.5.3, 13.5.4, 13.6.0, 13.6.1, 13.6.2, 13.6.3, 13.6.4

@microsoft/aspire-cli

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

@microsoft/aspire-cli-linux-x64

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

@microsoft/aspire-cli-linux-arm64

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

@microsoft/aspire-cli-linux-musl-x64

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

@microsoft/aspire-cli-osx-x64

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

@microsoft/aspire-cli-osx-arm64

npm

SEMVER · introduced 13.4.2 → fixed 13.6.5

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 18 Nov 16:53 UTC · 273 of 275 readable · 271 fully read · documentation 469/469 current