Vulnerability DatabaseCVE-2026-120778

CVE-2026-120778: 
JavaScript vulnerability analysis and mitigation

Overview

CVE-2026-120778 is a local privilege escalation vulnerability in Microsoft's .NET Aspire CLI caused by the creation of temporary files in directories with insecure permissions. It affects the Aspire.Cli NuGet package versions 13.2.0 through 13.6.4 and the @microsoft/aspire-cli npm packages versions 13.4.2 through 13.6.4, on Linux and macOS platforms (Windows is not affected). The vulnerability was disclosed on November 10, 2026, as part of Microsoft's November 2026 Patch Tuesday, with a patch released the same day. It carries a CVSS v3.1 base score of 7.3 (High) (MSRC, Github Advisory).

Technical details

The root cause is classified as CWE-379 (Creation of Temporary File in Directory with Insecure Permissions). The Aspire CLI uses an insecure temporary directory during CLI-generated server and integration builds, which allows a local attacker with write access to a shared temporary-directory ancestor to influence automatic MSBuild response-file discovery. By placing a malicious MSBuild response file in the attacker-writable directory, the attacker can cause the Aspire CLI to load it during builds triggered by aspire sdk generate, aspire sdk dump, or aspire sdk export commands, ultimately executing code with the privileges of the developer running the CLI. Exploitation requires low privileges and user interaction (a legitimate user must invoke the affected CLI commands) (Github Advisory, MSRC).

Impact

Successful exploitation allows a low-privileged local attacker to elevate their privileges to those of the developer running the Aspire CLI, resulting in high confidentiality, integrity, and availability impact on the affected system. An attacker could execute arbitrary code in the context of the targeted developer's account, potentially accessing sensitive source code, credentials, or build artifacts, and disrupting development workflows. The scope is limited to non-Windows systems (Linux and macOS) where shared temporary directories are accessible to multiple local users (Github Advisory, MSRC).

Exploitability

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at the time of disclosure (Github Advisory). The vulnerability is not automatable (requires user interaction) and is limited to local attack vectors, reducing its overall exploitability. The EPSS score is 0.0, reflecting a very low probability of exploitation in the near term. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. The vulnerability was reported by researcher l8BL with ENKI WhiteHat (Github Advisory).

Exploitation steps

  1. Reconnaissance: Identify a target system (Linux or macOS) where a developer is using a vulnerable version of the Aspire CLI (Aspire.Cli >= 13.2.0, < 13.6.5 or @microsoft/aspire-cli >= 13.4.2, < 13.6.5) and where the attacker has write access to a shared temporary-directory ancestor used by the CLI.
  2. Stage malicious MSBuild response file: In the attacker-writable shared temporary directory, create a malicious MSBuild response file (.rsp) containing arbitrary MSBuild targets or tasks designed to execute attacker-controlled code.
  3. Wait for user interaction: Wait for a legitimate developer to invoke an affected Aspire CLI command such as aspire sdk generate, aspire sdk dump, or aspire sdk export, which triggers a CLI-generated build.
  4. Privilege escalation via MSBuild: The Aspire CLI's build process automatically discovers MSBuild response files from the insecure temporary directory, loading the attacker's malicious file and executing its contents with the privileges of the developer running the CLI.
  5. Achieve objective: The attacker's code runs in the context of the targeted developer, enabling access to sensitive build artifacts, credentials, source code, or further lateral movement within the development environment (Github Advisory).

Indicators of compromise

  • File System: Unexpected or unfamiliar .rsp (MSBuild response) files in shared temporary directories (e.g., /tmp or world-writable subdirectories); files owned by a low-privileged user in directories used by the Aspire CLI build process.
  • Process: Unusual child processes spawned by the Aspire CLI or MSBuild process (e.g., shells, network utilities, or scripts not expected during a normal build); MSBuild executing tasks referencing files in /tmp or other shared directories.
  • Logs: Build logs showing unexpected MSBuild response file discovery from temporary directories; errors or warnings related to MSBuild response-file loading from atypical paths.
  • File System: New or modified files in the developer's home directory, SSH keys, or credential stores following an Aspire CLI build invocation (Github Advisory).

Mitigation and workarounds

Update the Aspire CLI to version 13.6.5 or later, which addresses the insecure temporary directory handling. If installed as a .NET tool, update the Aspire.Cli NuGet package; if installed via npm, update @microsoft/aspire-cli and ensure all platform-specific dependencies also resolve to version 13.6.5 or later. Note that updating the .NET runtime or SDK does not update the Aspire CLI, as Aspire ships independently. No configuration-based workaround is documented; upgrading is the recommended remediation (MSRC, Github Advisory).

Community reactions

CVE-2026-120778 was covered as part of broader reporting on Microsoft's November 2026 Patch Tuesday, which addressed over 1,000 security flaws. Coverage appeared in outlets including BleepingComputer and CyberSecurityNews, though the vulnerability itself received limited individual attention given its local-only attack vector and lack of active exploitation. No notable independent researcher commentary or significant social media discussion specific to this CVE has been identified beyond standard Patch Tuesday roundups (BleepingComputer, CyberSecurityNews).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

devel

dotnet10

Not Affected

jammy

dotnet6

Not Affected

noble

dotnet8

Not Affected

resolute

dotnet10

Not Affected

Source: This report was generated using AI

Related JavaScript vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

GHSA-g78f-3cr8-fhw5MEDIUM6.5
  • JavaScript logoJavaScript
  • imapflow
NoYesNov 15, 2026
GHSA-4j79-qhcg-f5wvMEDIUM6.4
  • JavaScript logoJavaScript
  • systeminformation
NoYesNov 15, 2026
GHSA-fcj7-c534-vj7fMEDIUM5.9
  • JavaScript logoJavaScript
  • find-my-way
NoNoNov 15, 2026
GHSA-chpj-828m-9wj6MEDIUM4.8
  • JavaScript logoJavaScript
  • karakeep
NoYesNov 15, 2026
GHSA-xcgp-hwgr-q92jLOW3.5
  • JavaScript logoJavaScript
  • karakeep
NoYesNov 15, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management