Repository navigation
Move Aspire to 13.6.5, for GHSA-f7vh-h5g3-7jrh - #5
Merged
Merged
Conversation
Aspire.Hosting and Aspire.Hosting.AppHost below 13.6.5 carry a high-severity elevation-of-privilege advisory (CVE-2026-120006). NuGet's audit treats it as an error, so restore fails, and CI with it. Only the local AppHost uses Aspire; no shipped package depends on it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Moves Aspire from 13.6.4 to 13.6.5:
Directory.Packages.props;Aspire.AppHost.Sdk;ARCHITECTURE-SLICES.md.Why
GHSA-f7vh-h5g3-7jrh (CVE-2026-120006) is a
high-severity elevation-of-privilege advisory for
Aspire.HostingandAspire.Hosting.AppHostbelow13.6.5. NuGet's audit treats it as an error, so
dotnet restore(CI's first step) fails on 13.6.4.Only the local AppHost uses Aspire; no shipped package depends on it, so nothing that consumes the sample
is affected.
Verified locally
dotnet restore --force-evaluate(fresh vulnerability data) and a Release build of the wholesolution, AppHost included: 0 errors, and 6 warnings, all Source Link's "Source control
information is not available", which
mainalready had. (Corrected after merging: this line firstsaid 0 warnings, from a count that missed warnings without a code.)
-p:UseLocalDotNetBoost=false):DotNetBoostSample.Tests 163, all pass.
Merge with the others
The same bump is going into the other DotNetBoost repositories. They share one
Aspire.AppHost.Sdkversion so they can build in one local workspace, so these should merge close together.
🤖 Generated with Claude Code