GHSA-F7VH-H5G3-7JRH
Vulnerability from github – Published: 2026-11-10 23:24 – Updated: 2026-11-10 23:24Executive 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.
Disclosure of an Aspire Dashboard authentication cookie to a linked service can allow an attacker-controlled container to replay the authenticated session and execute code as the host developer.
Announcement
Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/503
CVSS Details
- Version: 3.1
- Severity: High
- Score: 7.5
- Vector:
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H - Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)
Affected Platforms
- Platforms: macOS
- Architectures: x64, Arm64
Affected Packages
Standalone Aspire
| Package | Affected version | Patched version |
|---|---|---|
| Aspire.Hosting.AppHost | < 13.6.5 | 13.6.5 |
| Aspire.Hosting | < 13.6.5 | 13.6.5 |
The affected scenario involves a Dashboard-authenticated AppHost workflow with an attacker-controlled container and a linked HTTPS YARP gateway. The affected hosting code is in Aspire.Hosting, a dependency of Aspire.Hosting.AppHost. Aspire.AppHost.Sdk supplies the AppHost package implicitly unless the project overrides the default references.
Advisory FAQ
How do I know if I am affected?
The reported scenario involves a developer starting an Aspire AppHost, authenticating to its Dashboard, and following a resource link that routes to an attacker-controlled container. All released versions 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 components have been updated.
How do I fix the issue?
Update the AppHost project's Aspire.Hosting.AppHost package reference to version 13.6.5 or later. If the project obtains this package implicitly through Aspire.AppHost.Sdk, update that SDK reference to version 13.6.5 or later. Explicit package references or central version pins must also resolve Aspire.Hosting to version 13.6.5 or later. Restore dependencies, rebuild, and restart the AppHost after updating.
Updating only the .NET runtime, .NET SDK, Aspire CLI, or standalone Dashboard does not replace the AppHost project's hosting dependencies.
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.
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
Acknowledgements
- samthewhitehat
Revisions
V1.0 (November 10, 2026): Advisory published.
{
"affected": [
{
"package": {
"ecosystem": "NuGet",
"name": "Aspire.Hosting.AppHost"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "13.6.5"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "NuGet",
"name": "Aspire.Hosting"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "13.6.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-120006"
],
"database_specific": {
"cwe_ids": [
"CWE-201"
],
"github_reviewed": true,
"github_reviewed_at": "2026-11-10T23:24:48Z",
"nvd_published_at": "2026-11-10T19:20:26Z",
"severity": "HIGH"
},
"details": "## Executive summary\n\nMicrosoft is releasing this security advisory to provide information about a vulnerability in Aspire. This advisory provides guidance on updating affected applications and components.\n\nDisclosure of an Aspire Dashboard authentication cookie to a linked service can allow an attacker-controlled container to replay the authenticated session and execute code as the host developer.\n\n## Announcement\n\nAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/503\n\n## CVSS Details\n\n- **Version:** 3.1\n- **Severity:** High\n- **Score:** 7.5\n- **Vector:** `CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H`\n- **Weakness:** CWE-201 (Insertion of Sensitive Information Into Sent Data)\n\n## Affected Platforms\n\n- **Platforms:** macOS\n- **Architectures:** x64, Arm64\n\n## \u003ca name=\"affected-packages\"\u003e\u003c/a\u003eAffected Packages\n\n### Standalone Aspire\n\nPackage | Affected version | Patched version\n--- | --- | ---\n[Aspire.Hosting.AppHost](https://www.nuget.org/packages/Aspire.Hosting.AppHost) | \u003c 13.6.5 | 13.6.5\n[Aspire.Hosting](https://www.nuget.org/packages/Aspire.Hosting) | \u003c 13.6.5 | 13.6.5\n\nThe affected scenario involves a Dashboard-authenticated AppHost workflow with an attacker-controlled container and a linked HTTPS YARP gateway. The affected hosting code is in `Aspire.Hosting`, a dependency of `Aspire.Hosting.AppHost`. `Aspire.AppHost.Sdk` supplies the AppHost package implicitly unless the project overrides the default references.\n\n## Advisory FAQ\n\n### \u003ca name=\"how-affected\"\u003e\u003c/a\u003eHow do I know if I am affected?\n\nThe reported scenario involves a developer starting an Aspire AppHost, authenticating to its Dashboard, and following a resource link that routes to an attacker-controlled container. All released versions through 13.6.4 are affected.\n\nAspire ships independently of .NET. Installing a .NET runtime or SDK update does not establish that the affected Aspire components have been updated.\n\n### \u003ca name=\"how-fix\"\u003e\u003c/a\u003eHow do I fix the issue?\n\nUpdate the AppHost project\u0027s `Aspire.Hosting.AppHost` package reference to version 13.6.5 or later. If the project obtains this package implicitly through `Aspire.AppHost.Sdk`, update that SDK reference to version 13.6.5 or later. Explicit package references or central version pins must also resolve `Aspire.Hosting` to version 13.6.5 or later. Restore dependencies, rebuild, and restart the AppHost after updating.\n\nUpdating only the .NET runtime, .NET SDK, Aspire CLI, or standalone Dashboard does not replace the AppHost project\u0027s hosting dependencies.\n\n## Other Information\n\n### Reporting Security Issues\n\nIf 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).\n\nSecurity 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.\n\n### Support\n\nYou can ask questions about this issue in the [Aspire repository](https://github.com/microsoft/aspire).\n\n### Disclaimer\n\nThe 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.\n\n### External Links\n\n[CVE-2026-120006](https://www.cve.org/CVERecord?id=CVE-2026-120006)\n\n### Acknowledgements\n\n- samthewhitehat\n\n### Revisions\n\nV1.0 (November 10, 2026): Advisory published.",
"id": "GHSA-f7vh-h5g3-7jrh",
"modified": "2026-11-10T23:24:48Z",
"published": "2026-11-10T23:24:48Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/microsoft/aspire/security/advisories/GHSA-f7vh-h5g3-7jrh"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120006"
},
{
"type": "WEB",
"url": "https://github.com/dotnet/announcements/issues/503"
},
{
"type": "WEB",
"url": "https://github.com/microsoft/aspire/issues/22092"
},
{
"type": "WEB",
"url": "https://github.com/microsoft/aspire/commit/f017f668fd6e0938e23058dc0450a1403f409809"
},
{
"type": "PACKAGE",
"url": "https://github.com/microsoft/aspire"
},
{
"type": "WEB",
"url": "https://github.com/microsoft/aspire/releases/tag/v13.6.5"
},
{
"type": "WEB",
"url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-120006"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Microsoft Security Advisory CVE-2026-120006 - Aspire Elevation of Privilege Vulnerability"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.