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.
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.
[HIGH] CVE identifier year appears incorrect:
CVE-2026-31431should likely beCVE-2025-31431The CVE identifier uses the year
2026, which is a future year. CVEs are assigned in the year they are reported, soCVE-2026-31431would be anachronistic. This is almost certainly a typo — the correct identifier is likelyCVE-2025-31431(or possiblyCVE-2024-31431).An incorrect CVE number prevents users from looking up this vulnerability in NVD or MITRE and could mislead security teams researching the fix.