Home › Vulnerabilities

Microsoft Aspire Dashboard Flaw CVE-2026-118740: Update Now

Published November 12, 2026 · Last updated November 12, 2026

CVE Critical Patch

The short version: CVE-2026-118740 is a critical-severity security flaw in Microsoft Aspire Dashboard. The National Vulnerability Database (NVD) published it on November 10, 2026, and the score it lists is 9.1 out of 10. When FraudMeNot checked on November 12, 2026, CISA had not added CVE-2026-118740 to its Known Exploited Vulnerabilities catalog, so there was no public U.S. government confirmation of attacks yet. A fix is available, which is why this page focuses on who should update and how.

CVE-2026-118740 is a critical missing-authorization flaw in Microsoft’s Aspire Dashboard. Microsoft’s security advisory says the Dashboard’s unauthenticated NotFound route can permit telemetry deletion in both standalone deployments and deployments launched by an Aspire AppHost. In standalone deployments that use browser-token authentication, the same route can also expose the browser token. The weakness is CWE-862. An unauthenticated attacker can reach the issue over the network; no user interaction is required.

Microsoft, the CVE Numbering Authority, scores it CVSS 3.1 9.1 CRITICAL, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. The GitHub advisory that published the full Microsoft bulletin uses the same figure as its headline. NVD records that 9.1 score as Secondary, source the address listed on microsoft.com; vulnStatus is Awaiting Analysis, and NVD has not assigned a Primary score of its own. There is no CVSS 4.0. The selection rule prefers V31, then V40, then V30, so the selected score is CVSS 3.1 9.1. That is well above the 7.0 floor. The vendor headline is also 9.1 Critical.

Who is affected

Microsoft says Aspire Dashboard releases through 13.6.4 are affected, whether the Dashboard is deployed independently or launched by an Aspire AppHost. The CVE record’s affected range starts at 13.6.1 and ends before 13.6.5, on Linux and Windows, for the standalone Dashboard and for the Aspire.Dashboard.Sdk packages (linux-x64 and other platform-specific SDK packages listed in the advisory). The bulletin is explicit that both 13.6.3 and 13.6.4 still contain the unauthenticated NotFound route, so those two point releases are not a sufficient upgrade.

For an AppHost that uses Dashboard SDK packages, operators should compare the resolved Aspire.Dashboard.Sdk package versions with the ranges above. If the AppHost selects a CLI-bundled Dashboard or a custom Dashboard path, they should check the version of that Dashboard instead. Aspire ships independently of the .NET runtime: installing a .NET runtime or SDK update does not replace the Dashboard.

The advisory applies on any supported operating system, on x64 and Arm64.

What to install, and who acts

The fixed release is Aspire Dashboard 13.6.5 or later. Microsoft’s “How do I fix the issue?” section is specific about the different ways the Dashboard is shipped, and those differences matter.

Operators of Aspire Dashboard—application teams and platform engineers who run a standalone Dashboard, an AppHost-hosted Dashboard, or a container image—should apply the matching path below. Updating one layer is not a substitute for the others.

  • For container deployments, set the Dashboard image explicitly to mcr.microsoft.com/aspire/dashboard:13.6.5 and recreate or redeploy the container. Replace older version tags and nightly image references, including those in generated Docker Compose or Kubernetes manifests, with this fixed stable image. Updating AppHost package references alone does not replace an image reference in an existing deployment manifest.
  • For an AppHost that uses Dashboard SDK packages, update any explicit Aspire.Hosting.AppHost version, including a central package version, to 13.6.5 or later. If that reference is supplied implicitly by Aspire.AppHost.Sdk, update the SDK reference to 13.6.5 or later instead. Restore and rebuild the AppHost, verify that the resolved Aspire.Dashboard.Sdk packages are 13.6.5 or later, and restart the AppHost so it runs the updated Dashboard.
  • If the AppHost selects a CLI-bundled Dashboard or a custom Dashboard path, update the Dashboard in that selected bundle or location to 13.6.5 or later and restart the AppHost. Again, updating AppHost package references alone does not replace that Dashboard.

GitHub’s release tag v13.6.5, published 2026-11-10 at 21:45:33 UTC, is the matching fixed build.

What the 13.6.5 release notes say about the fix

GitHub’s Aspire 13.6.5 notes describe this as a “patch release for Aspire 13.6 with dashboard and CLI security hardening and .NET runtime servicing updates.” The Dashboard item that corresponds to the unauthenticated NotFound route is titled “Dashboard authentication is enforced on missing and unauthorized routes.” On a secured Dashboard, authorization is now checked before the main layout is rendered for missing routes or denied access. In browser-token mode, unauthenticated users are redirected to login with the original route preserved. Additional authentication checks protect layout, dialog, interaction, and standalone terminal-window initialization. Unsecured mode is unchanged.

The same notes record a related hardening: container telemetry no longer implicitly exposes the Dashboard frontend. When the Aspire container tunnel is enabled, automatic Dashboard tunneling exposes only the OTLP gRPC and HTTP endpoints. Explicit references to other Dashboard endpoints remain supported, and tunneling for ordinary host-resource dependencies is unchanged.

Two further CLI-side hardenings ship in the same tag, and operators who use those tools pick them up by installing this release:

  • CLI-generated AppHost server and integration builds now ignore automatic MSBuild response files, without changing user-authored builds or support for explicitly supplied response files. The aspire sdk generate, aspire sdk dump, and aspire sdk export commands use isolated working directories under /tmp/sdk/, with owner-only Unix permissions, local configuration isolation, and cleanup when the command finishes. Normal AppHost caches are unchanged.
  • aspire agent init stops writing agent configuration paths, configuration content, and scan diagnostics to aspire-deprecated-scan.log in the operating system’s temporary directory. Deprecated MCP command detection, migration prompts, configuration updates, and existing structured debug logging are preserved. Previously written temporary log files are not removed by this update.

The notes also refresh bundled runtimes and .NET servicing dependencies, including .NET 10.0.14, 9.0.22, and 8.0.33, for servicing fixes relevant to Native AOT process startup. Those runtime bumps are part of the same package; they are not a substitute for moving the Dashboard itself to the fixed release.

Score, window, and sources

Selected score: CVSS 3.1 9.1 CRITICAL, CNA Microsoft, NVD Secondary; vendor and GitHub advisory headline 9.1. First official announcement: Microsoft’s datePublic 2026-11-10T16:00:00.000Z (11:00 AM EST November 10), consistent with the bulletin’s “V1.0 (November 10, 2026): Advisory published” revision line and with the CVE record’s publication at 2026-11-10T18:24:15.124Z. The 72-hour window ends November 13, 2026 at 11:00 AM EST. This 2PM slot is inside that window.

A short GitHub Security Advisory for this CVE appeared on November 10 and was later marked a duplicate. The full Microsoft bulletin text was published in GHSA-4g86-54fm-h9h8 on November 12 at 17:17 UTC (12:17 PM EST), which is why this slot can support a complete page from official sources. The underlying first-announcement clock still starts on November 10.

The advisory credits Weeraphat Srisutham. Microsoft’s announcement issue is #526 in the dotnet/announcements repository (opened November 11). NVD’s lastModified on the record as of this check is 2026-11-11T12:19:10.087Z; CISA’s ADP SSVC entry from November 10 records Exploitation: none, Automatable: no, and Technical Impact: partial.

Sources: Microsoft security advisory as published in GHSA-4g86-54fm-h9h8 and at https://github.com/microsoft/aspire/security/advisories/GHSA-4g86-54fm-h9h8; .NET announcement issue 526; Aspire release notes for v13.6.5 (published 2026-11-10 21:45:33 UTC); CVE record CVE-2026-118740 (CNA Microsoft, datePublic 2026-11-10T16:00:00.000Z); NVD CVE-2026-118740.

What the official record says about CVE-2026-118740

The record was filed by microsoft.com. In its own words: "Missing authorization in Aspire allows an unauthorized attacker to bypass a security feature over a network."

Why Aspire Dashboard admins should care

Severity scores use the Common Vulnerability Scoring System (CVSS). the address listed on microsoft.com rated CVE-2026-118740 9.1 (Critical) under CVSS 3.1. Reading that rating in everyday terms: it can be reached over a network, including the internet; an attacker does not need an account; no one has to click or open anything. If it is abused, the rated damage to keeping data private is high, to keeping data unaltered is high, and to keeping Aspire Dashboard running is none. Scoring string: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N.

Affected Aspire Dashboard releases

According to the record, these releases are vulnerable:

  • 13.6.1 up to, but not including, 13.6.5
  • 13.6.1 up to, but not including, 13.6.5

The type of bug behind CVE-2026-118740

NVD classifies it using MITRE's Common Weakness Enumeration:

  • CWE-862, Missing Authorization. MITRE describes this class of bug as follows: "The product does not perform an authorization check when an actor attempts to access a resource or perform an action."

Vendor remediation for CVE-2026-118740

The vendor advisory remediation for operators of Aspire Dashboard, quoted for this page, is: "Upgrade Aspire Dashboard to 13.6.5 or later. For containers, set the image to mcr.microsoft.com/aspire/dashboard:13.6.5 and redeploy; for AppHost, update Aspire.Hosting.AppHost or Aspire.AppHost.Sdk to 13.6.5, restore, rebuild, and restart. 13.6.3 and 13.6.4 are not fixed. A .NET runtime update does not replace the Dashboard."

What to do about it

  • Update now: Upgrade Aspire Dashboard to 13.6.5 or later. For containers, set the image to mcr.microsoft.com/aspire/dashboard:13.6.5 and redeploy; for AppHost, update Aspire.Hosting.AppHost or Aspire.AppHost.Sdk to 13.6.5, restore, rebuild, and restart. 13.6.3 and 13.6.4 are not fixed. A .NET runtime update does not replace the Dashboard.
  • Who should act: IT teams, managed service providers, and developers who run or ship Aspire Dashboard. Check every place it runs, including servers, build systems, containers, and older machines nobody watches closely.
  • Read the official advisory from Microsoft (linked under Sources) for exact fixed builds and any temporary workaround if you cannot patch today.
  • After patching, confirm the new version is actually running and review logs from November 10, 2026 onward for anything unusual.
  • Home users: you do not need to buy or download anything because of CVE-2026-118740. A caller, text, or pop-up claiming your computer is "infected" with this CVE and asking for money or remote access is a scam.

CVE-2026-118740 record details from CISA and NVD

  • Attack complexity for CVE-2026-118740: low
  • CVE-2026-118740 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-118740: exploitability 3.9, impact 5.2.
  • Who mapped the weakness type: the address listed on microsoft.com (Secondary)
  • References in the NVD record: 1.
  • CISA SSVC decision points for CVE-2026-118740 (from NVD): exploitation=none; automatable=no; technicalImpact=partial (role: CISA Coordinator, SSVC 2.0.3).

Dates to know

  • November 10, 2026: NVD publishes CVE-2026-118740.
  • November 12, 2026: FraudMeNot checks the CISA KEV catalog; CVE-2026-118740 is not listed.
  • November 11, 2026: most recent NVD update (record status: Awaiting Analysis).

Official references

Links listed in the NVD record (labels in brackets come from NVD):

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.