fix(server): pin MessagePack to remediate GHSA-hv8m-jj95-wg3x#94
Merged
Merged
Conversation
StreamJsonRpc 2.20.20 transitively pulls MessagePack 2.5.187, which has a known high severity vulnerability (NU1903). With warnings-as-errors enabled, this fails restore/build in CI. Pin MessagePack to 2.5.302, the latest patched 2.5.x release.
35bb5ff to
88f0656
Compare
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.
Summary
CI builds are failing during NuGet restore with
NU1903(warning-as-error):MessagePack 2.5.187is pulled in transitively byStreamJsonRpc 2.20.20inCodingWithCalvin.MCPServer.Server. Because the build treats warnings as errors, the advisory blocks every build — including unrelated PRs such as #93.Change
Add a direct
PackageReferencetoMessagePack2.5.302(latest patched2.5.x, advisory fixed in2.5.192) to override the vulnerable transitive version.Validation
dotnet publishof the Server project now restores and builds cleanly with noNU1903error.