-
Notifications
You must be signed in to change notification settings - Fork 438
[GHSA-h4j7-5rxr-p4wc] Microsoft.Build.Tasks.Core .NET Spoofing Vulnerability #5718
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.
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
[GHSA-h4j7-5rxr-p4wc] Microsoft.Build.Tasks.Core .NET Spoofing Vulnerability #5718
Conversation
Hi there @rbhanda! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR addresses discrepancies in CVSS ratings for the Microsoft.Build.Tasks.Core .NET Spoofing Vulnerability advisory by updating the severity section and a modified timestamp in the JSON file.
- Updated modified timestamp.
- Removed the CVSS_V3 severity object in favor of using the CVSS_V4 score only.
Comments suppressed due to low confidence (1)
advisories/github-reviewed/2025/05/GHSA-h4j7-5rxr-p4wc/GHSA-h4j7-5rxr-p4wc.json:11
- Removing the CVSS_V3 severity object may lead to discrepancies with external CVSS ratings referenced in the advisory comments. Consider adding a clarifying note in the advisory details to specify that only the CVSS_V4 score is used to ensure consistency across sources.
{ "type": "CVSS_V3", "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H" }
Hi there @rbhanda! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
Hi there @rbhanda! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
@victorisr, @rbhanda please also update your announcement here: GHSA-h4j7-5rxr-p4wc |
1708111
into
udlose/advisory-improvement-5718
Hi @udlose! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
Hi @udlose, I agree with changing the CVSS of GHSA-h4j7-5rxr-p4wc to match the CVSS chosen by the Microsoft Corporation CNA. I can't change the repository advisory, but the global advisory has been updated to reflect the CVSS provided at https://nvd.nist.gov/vuln/detail/CVE-2025-26646. |
Updates
Comments
Low
for this advisory does not match the CVSS rating ofHigh
in CVE.org - CVE-2025-266460/10
for this advisory does not match the CVSS rating of8.0
in CVE.org - CVE-2025-26646