Add CVSS 3.1 score for GHSA-r6ph-v2qm-q3c2 (cryptography Subgroup Attack) #6852
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.
Changes
Added missing CVSS 3.1 scoring to GHSA-r6ph-v2qm-q3c2 (Python cryptography Subgroup Attack on SECT Curves).
Added:
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N(7.4 High)Reason for change
This advisory had no CVSS 3.1 score. NVD only provides CVSS 4.0 scoring (8.2) for CVE-2026-26007. Adding a CVSS 3.1 vector ensures broader compatibility with vulnerability management tools that rely on CVSS 3.1 for severity assessment.
CVSS justification
VI:Nbut this underrates the integrity impact: private key recovery directly enables forging signatures for the same key pairThe difference from the CVSS 4.0 vector (which uses
VI:N) is justified because subgroup attacks on elliptic curves are a well-documented class that enables both key recovery (C:H) and signature forgery (I:H). Discovered by Tencent Xuanwu Lab's Atuin Automated Vulnerability Discovery Engine.Supporting links