Skip to content

Rename CVE-2022-31126->CVE-2022-31137 #12103

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
May 20, 2025
Merged

Rename CVE-2022-31126->CVE-2022-31137 #12103

merged 1 commit into from
May 20, 2025

Conversation

@ritikchaddha
Copy link
Contributor

@ritikchaddha ritikchaddha commented May 20, 2025

Template / PR Information

  • Fixed CVE-2020-XXX / Added CVE-2020-XXX / Updated CVE-2020-XXX
  • References:

Template Validation

I've validated this template locally?

  • YES
  • NO

Additional Details (leave it blank if not applicable)

Additional References:

@ritikchaddha ritikchaddha self-assigned this May 20, 2025
@ritikchaddha ritikchaddha added the Done Ready to merge label May 20, 2025
@github-actions github-actions bot requested a review from pussycat0x May 20, 2025 06:49
@ritikchaddha ritikchaddha merged commit 8233ce9 into main May 20, 2025
4 checks passed
@ritikchaddha ritikchaddha deleted the CVE-2022-31137 branch May 20, 2025 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pussycat0x pussycat0x Awaiting requested review from pussycat0x

Assignees

@ritikchaddha ritikchaddha

Labels

Done Ready to merge

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ritikchaddha