Bump System.Security.Cryptography.Xml to the advisory-patched versions#532
Merged
ITaluone merged 1 commit intoJul 23, 2026
Merged
Conversation
10.0.6, 9.0.15 and 8.0.3 are all inside the affected ranges of five high-severity advisories (GHSA-23rf-6693-g89p, GHSA-8q5v-6pqq-x66h, GHSA-cvvh-rhrc-wg4q, GHSA-g8r8-53c2-pm3f, GHSA-mmjf-rqrv-855v) — uncontrolled resource consumption in XML decryption. Move each line to its first patched release: 10.0.10, 9.0.18, 8.0.4. Fallout.Common carries the package as a direct dependency, so every consumer inherits the vulnerable version transitively and has to pin around it locally. Both the central version list and build/_build.csproj are bumped; the build project turns off central package management, so its inline pin is separate. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lahma
marked this pull request as ready for review
July 23, 2026 08:46
This was referenced Jul 23, 2026
ITaluone
approved these changes
Jul 23, 2026
ITaluone
left a comment
ITaluone
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for fixing this
And: welcome to the repo 😄
ChrisonSimtian
approved these changes
Jul 23, 2026
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
3 participants
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.
System.Security.Cryptography.Xmlis pinned at versions inside the affected range of five high-severity advisories — uncontrolled resource consumption during XML decryption (CVSS 7.5):Each line moves to its first patched release:
Fallout.Commondeclares the package as a direct dependency, so consumers inherit the vulnerable version transitively andNuGetAuditfires on their build project — the only fix on their side is a local pin. Migrating Quartz.NET off NUKE surfaced this; it currently has to carry:Both the central version list and
build/_build.csprojare bumped — the build project turns off central package management, so its inline pin is separate.dotnet restore fallout.slnxis clean for everysrc/project afterwards.tests/Consumers/Fallout.Consumer.NuGetstill warns because it resolves the publishedFallout.Commonfrom nuget.org; that clears once a release ships with this bump.🤖 Generated with Claude Code