Skip to content

fix(deps): pin MessagePack 2.5.303 for GHSA-qhrr-8q5h-9q3h - #1321

Merged
mforce merged 1 commit into
mainfrom
chore/messagepack-ghsa-qhrr
Oct 16, 2026
Merged

mforce merged 1 commit into
mainfrom
chore/messagepack-ghsa-qhrr

Conversation

@mforce

@mforce mforce commented Oct 16, 2026

Copy link
Copy Markdown
Owner

GHSA-qhrr-8q5h-9q3h (MessagePack < 2.5.303, moderate) was published on 2026-10-15. NuGet audit raises it as NU1902, which this repo treats as an error, so dotnet restore fails in both AppHost projects. Every PR's .NET jobs now fail in about 20 seconds; #1315 is one example.

MessagePack 2.5.302 comes in transitively through Aspire.Hosting 13.6.1 and StreamJsonRpc. This PR pins 2.5.303 in Directory.Packages.props and adds a direct reference in Cluckwork.AppHost.csproj, the same way Microsoft.OpenApi is pinned. AppHost.Tests gets the pin through its project reference.

Both lock files change only their MessagePack entries. A plain restore also moved the floating Microsoft.NET.Test.Sdk and xunit.runner.visualstudio ranges in AppHost.Tests. I removed those unrelated changes from the AppHost.Tests lock file.

Verified locally:

  • dotnet restore Cluckwork.slnx --locked-mode passes.
  • The solution builds with 0 errors.
  • dotnet list package --vulnerable --include-transitive reports nothing in any project.

Remove the pin once Aspire ships a patched dependency.

Aspire.Hosting 13.6.1 and StreamJsonRpc resolve MessagePack 2.5.302.
GHSA-qhrr-8q5h-9q3h, published 2026-10-15, makes restore fail with
NU1902 in both AppHost projects, so every PR's .NET jobs go red.

Pin the patched 2.5.303 centrally with a direct reference in the
AppHost, the same pattern as the Microsoft.OpenApi pin. The lock files
change only the MessagePack entries.
@mforce
mforce merged commit 60f7e70 into main Oct 16, 2026
22 checks passed
@mforce
mforce deleted the chore/messagepack-ghsa-qhrr branch October 16, 2026 17:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant