GHSA-4g86-54fm-h9h8: Microsoft Security Advisory CVE-2026-118740 - Aspire Security Feature Bypass Vulnerability

Published Nov 12, 2026
·
Updated

Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in Aspire. This advisory provides guidance on updating affected applications and components.

Aspire Dashboard's unauthenticated NotFound route can permit telemetry deletion in both standalone and AppHost-hosted deployments. In standalone deployments using browser-token authentication, it can also expose the browser token.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/526

CVSS Details

- Version: 3.1 - Severity: Critical - Score: 9.1 - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N - Weakness: CWE-862

Affected Platforms

- Platforms: Any supported OS - Architectures: x64, Arm64

<a name="affected-packages"></a>Affected Packages

Standalone Aspire Dashboard

Package | Affected version | Patched version --- | --- | --- Aspire Dashboard | < 13.6.5 | 13.6.5

Both 13.6.3 and 13.6.4 contain the unauthenticated NotFound route.

Aspire Dashboard SDK packages

Package | Affected version | Patched version --- | --- | --- Aspire.Dashboard.Sdk.linux-x64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.linux-arm64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.linux-musl-x64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.osx-x64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.osx-arm64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.win-x64 | < 13.6.5 | 13.6.5 Aspire.Dashboard.Sdk.win-arm64 | < 13.6.5 | 13.6.5

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

Aspire Dashboard releases through 13.6.4 are affected, whether deployed independently or launched by an Aspire AppHost. For an AppHost using Dashboard SDK packages, check the resolved Aspire.Dashboard.Sdk package versions against the affected ranges above. If the AppHost selects a CLI-bundled Dashboard or a custom Dashboard path, check the version of that Dashboard instead. Aspire ships independently of .NET; installing a .NET runtime or SDK update does not replace the Dashboard.

<a name="how-fix"></a>How do I fix the issue?

Update Aspire Dashboard to version 13.6.5 or later. Neither 13.6.3 nor 13.6.4 is a fixed upgrade target.

For container deployments, explicitly set the Dashboard image 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 using 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 its resolved Aspire.Dashboard.Sdk packages are 13.6.5 or later, and restart the AppHost to run the updated Dashboard.

If your 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. Updating AppHost package references alone does not replace that Dashboard.

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. Further information can be found in the MSRC Report an Issue FAQ.

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 at https://github.com/microsoft/aspire. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

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-118740

Acknowledgements

- Weeraphat Srisutham

Revisions

V1.0 (November 10, 2026): Advisory published.

Affected Software

7 affected componentsFixes available
nuget/aspire.dashboard.sdk.win-arm64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.win-x64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.osx-arm64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.osx-x64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.linux-musl-x64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.linux-arm64<13.6.5
13.6.5
nuget/aspire.dashboard.sdk.linux-x64<13.6.5
13.6.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.win-arm64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  2. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.win-x64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  3. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.osx-arm64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  4. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.osx-x64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  5. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.linux-musl-x64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  6. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.linux-arm64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  7. Upgrade

    Upgrade nuget/Aspire.Dashboard.Sdk.linux-x64 to a version that resolves this vulnerability.

    Fixed in 13.6.5
  8. Upgrade

    Upgrade Aspire Dashboard to a version that resolves this vulnerability.

    Fixed in 13.6.5
  9. Upgrade

    Upgrade Aspire.Dashboard.Sdk packages to a version that resolves this vulnerability.

    Fixed in 13.6.5
  10. Upgrade

    Upgrade Aspire.Hosting.AppHost / Aspire.AppHost.Sdk to a version that resolves this vulnerability.

    Fixed in 13.6.5
  11. Upgrade

    Upgrade mcr.microsoft.com/aspire/dashboard to a version that resolves this vulnerability.

    Fixed in 13.6.5
  12. Operational

    For container deployments, replace older version tags and nightly image references with mcr.microsoft.com/aspire/dashboard:13.6.5 and recreate or redeploy the container. Restore and rebuild the AppHost, verify its resolved Aspire.Dashboard.Sdk packages are 13.6.5 or later, and restart the AppHost.

Event History

Nov 12, 2026
Advisory Published
via GitHub·05:17 PM
Data Sourced
via GitHub·05:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Which deployment types are exposed to telemetry deletion?

Both standalone Aspire Dashboard deployments and AppHost-hosted deployments are affected by the unauthenticated route that permits telemetry deletion.

2

When is browser-token exposure possible?

Browser-token exposure is specific to standalone Aspire Dashboard deployments that use browser-token authentication. The advisory does not identify this exposure for AppHost-hosted deployments.

3

What update is identified for standalone Aspire Dashboard installations?

Update Aspire Dashboard to version 13.6.5. Versions earlier than 13.6.5 are affected, and the advisory specifically notes that 13.6.3 and 13.6.4 contain the unauthenticated route.

4

Does exploitation require an authenticated user?

No. The issue is an unauthenticated route, and the provided CVSS vector indicates no privileges or user interaction are required.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203