Fix Microsoft.OpenApi high-severity vulnerability blocking builds#2319
Merged
Conversation
Microsoft.AspNetCore.OpenApi transitively pulls in Microsoft.OpenApi 2.0.0, which has a high-severity advisory (GHSA-v5pm-xwqc-g5wc) for circular schema references terminating OpenAPI parsing. NuGetAudit treats this as a build error, which has been silently failing the daily "Update Packages" workflow since the advisory was published and just blocked the Release-configuration Publish build outright. Pin the transitive dependency to the patched 2.7.5 release via central package management.
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.
Fixed
Microsoft.OpenApidependency by pinning it to the patched2.7.5release.Summary
Microsoft.AspNetCore.OpenApitransitively pulls inMicrosoft.OpenApi2.0.0, which has a known high-severity advisory for circular schema references terminating OpenAPI parsing. NuGetAudit treats this as a build error (NU1903), which has been silently failing the dailyUpdate Packagesworkflow since the advisory was published, and blocks any Release-configuration build outright.