[GHSA-ggv3-7p47-pfv8] Add missing CVSS 3.1 score from NVD assessment#7385
Open
PiniShv wants to merge 1 commit intogithub:PiniShv/advisory-improvement-7385from
Open
[GHSA-ggv3-7p47-pfv8] Add missing CVSS 3.1 score from NVD assessment#7385PiniShv wants to merge 1 commit intogithub:PiniShv/advisory-improvement-7385from
PiniShv wants to merge 1 commit intogithub:PiniShv/advisory-improvement-7385from
Conversation
github-actions
bot
changed the base branch from
main
to
PiniShv/advisory-improvement-7385
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
1 participant
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.
Change
Add the missing CVSS 3.1 score to GHSA-ggv3-7p47-pfv8 (CVE-2026-29057), the Next.js HTTP request smuggling vulnerability.
What was missing
The advisory currently includes only a CVSS 4.0 vector. NIST independently assessed a CVSS 3.1 score as part of their initial analysis on March 18, 2026:
Source: NVD - CVE-2026-29057
Why it matters
Many vulnerability scanners, SCA tools, and compliance frameworks still evaluate severity using CVSS 3.1. Without the 3.1 vector in the advisory data, these tools either skip the advisory or fall back to heuristic severity mapping, which can produce inaccurate results. Adding the NIST-assessed CVSS 3.1 alongside the existing CVSS 4.0 improves downstream data quality for consumers of the GitHub Advisory Database.
No other fields were changed.