# CVE-2026-120778: Aspire Elevation of Privilege Vulnerability


- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 10 Nov 2026
- **Updated:** 16 Nov 2026
- **Also known as:** GHSA-m63f-xhvm-6mv5, UBUNTU-CVE-2026-120778

## What is CVE-2026-120778?

CVE-2026-120778 is a high-severity vulnerability in Microsoft Aspire.Cli, published on 10 Nov 2026. 

### Official description

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

Weakness: CWE-379 (Creation of Temporary File in Directory with Insecure Permissions)

## Which versions are affected by CVE-2026-120778?

12 open source packages ship an affected version, including Aspire.Cli, Aspire.Cli.linux-arm64 and Aspire.Cli.linux-musl-x64.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `Aspire.Cli` | NuGet | `pkg:nuget/Aspire.Cli` | From 13.2.0 | 13.6.5 |
| `Aspire.Cli.linux-arm64` | NuGet | `pkg:nuget/Aspire.Cli.linux-arm64` | From 13.3.0 | 13.6.5 |
| `Aspire.Cli.linux-musl-x64` | NuGet | `pkg:nuget/Aspire.Cli.linux-musl-x64` | From 13.3.0 | 13.6.5 |
| `Aspire.Cli.linux-x64` | NuGet | `pkg:nuget/Aspire.Cli.linux-x64` | From 13.3.0 | 13.6.5 |
| `Aspire.Cli.osx-arm64` | NuGet | `pkg:nuget/Aspire.Cli.osx-arm64` | From 13.3.0 | 13.6.5 |
| `Aspire.Cli.osx-x64` | NuGet | `pkg:nuget/Aspire.Cli.osx-x64` | From 13.3.0 | 13.6.5 |
| `@microsoft/aspire-cli` | npm | `pkg:npm/%40microsoft/aspire-cli` | From 13.4.2 | 13.6.5 |
| `@microsoft/aspire-cli-linux-arm64` | npm | `pkg:npm/%40microsoft/aspire-cli-linux-arm64` | From 13.4.2 | 13.6.5 |
| `@microsoft/aspire-cli-linux-musl-x64` | npm | `pkg:npm/%40microsoft/aspire-cli-linux-musl-x64` | From 13.4.2 | 13.6.5 |
| `@microsoft/aspire-cli-linux-x64` | npm | `pkg:npm/%40microsoft/aspire-cli-linux-x64` | From 13.4.2 | 13.6.5 |
| `@microsoft/aspire-cli-osx-arm64` | npm | `pkg:npm/%40microsoft/aspire-cli-osx-arm64` | From 13.4.2 | 13.6.5 |
| `@microsoft/aspire-cli-osx-x64` | npm | `pkg:npm/%40microsoft/aspire-cli-osx-x64` | From 13.4.2 | 13.6.5 |

Status by vendor (upstream, then each distribution release and vendor build):

| Who | Release | Status | Packages | Fixed in |
| --- | --- | --- | --- | --- |
| Upstream |  | fixed | `@microsoft/aspire-cli`, `@microsoft/aspire-cli-linux-arm64`, `@microsoft/aspire-cli-linux-musl-x64` and 9 more | 13.6.5 |

## How do I fix CVE-2026-120778?

Upgrade Aspire.Cli to 13.6.5 or later.

## Is CVE-2026-120778 being exploited?

There is no known exploitation of CVE-2026-120778 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120778 and fix it if it is affected.

What it is: CVE-2026-120778 is a high-severity vulnerability in Microsoft Aspire.Cli, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-120778 in the wild and no public exploit code.

Affected packages and fixed versions:
- Aspire.Cli (NuGet): affected from 13.2.0; fixed in 13.6.5
- Aspire.Cli.linux-arm64 (NuGet): affected from 13.3.0; fixed in 13.6.5
- Aspire.Cli.linux-musl-x64 (NuGet): affected from 13.3.0; fixed in 13.6.5
- Aspire.Cli.linux-x64 (NuGet): affected from 13.3.0; fixed in 13.6.5
- Aspire.Cli.osx-arm64 (NuGet): affected from 13.3.0; fixed in 13.6.5
- Aspire.Cli.osx-x64 (NuGet): affected from 13.3.0; fixed in 13.6.5
- @microsoft/aspire-cli (npm): affected from 13.4.2; fixed in 13.6.5
- @microsoft/aspire-cli-linux-arm64 (npm): affected from 13.4.2; fixed in 13.6.5
- @microsoft/aspire-cli-linux-musl-x64 (npm): affected from 13.4.2; fixed in 13.6.5
- @microsoft/aspire-cli-linux-x64 (npm): affected from 13.4.2; fixed in 13.6.5
- @microsoft/aspire-cli-osx-arm64 (npm): affected from 13.4.2; fixed in 13.6.5
- @microsoft/aspire-cli-osx-x64 (npm): affected from 13.4.2; fixed in 13.6.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120778/ (Markdown: https://insights.sbomify.com/CVE-2026-120778/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120778
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120778
- OSV: https://osv.dev/vulnerability/CVE-2026-120778

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120778/
Summaries are generated and may contain mistakes; the official description above is the record.
