Skip to content

chore: pin NuGet transitives in build/ to clear 8 advisories #585

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jeremydmiller merged 1 commit into from
Jul 29, 2026
Merged

chore: pin NuGet transitives in build/ to clear 8 advisories #585

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 17 additions & 0 deletions build/Build.csproj
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,23 @@

<ItemGroup>
<PackageReference Include="Nuke.Common" Version="10.1.0" />

<!--
Nuke.Common 10.1.0 (the latest release) pulls NuGet.Packaging 6.12.1, which in turn pulls
System.Security.Cryptography.Xml 9.0.0 - seven high-severity advisories (NU1903). Nuke can't
be bumped past this, so pin the transitive up to the patched floor directly. 9.0.15 clears
only four of the seven; 9.0.18 covers all of them.

Nothing is shipped from build/, so this has no consumer impact. Drop the pin once Nuke ships
against a NuGet.Packaging that doesn't drag in a vulnerable version.
-->
<PackageReference Include="System.Security.Cryptography.Xml" Version="9.0.18" />

<!--
Same story one level up: NuGet.Packaging 6.12.1 carries the low-severity GHSA-g4vj-cjjj-v7hg
(NU1901). 6.12.5 is the patched release on the same 6.12.x line Nuke already builds against.
-->
<PackageReference Include="NuGet.Packaging" Version="6.12.5" />
</ItemGroup>

</Project>
Loading