Fix CVE-2025-26646: Update Nuke.Common to 9.0.4 and Microsoft.Build.Tasks.Core to 17.14.8 #74
Conversation
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
…asks.Core to 17.14.8
There was a problem hiding this comment.
Pull Request Overview
This PR addresses a high-severity security vulnerability (CVE-2025-26646) by updating build tool dependencies to patched versions that resolve an external control of file name or path vulnerability.
- Updates Nuke.Common from version 8.1.4 to 9.0.4
- Adds explicit dependency on Microsoft.Build.Tasks.Core version 17.14.8 to ensure the patched version is used
|
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.
This PR addresses the high-severity vulnerability CVE-2025-26646 by:
The vulnerability is related to external control of file name or path in .NET, Visual Studio, and Build Tools for Visual Studio, with a CVSS score of 8.0. The fix ensures we use the patched version of Microsoft.Build.Tasks.Core that resolves this security issue.