CVE-2026-62167 not published to GitHub Advisory Database

Open
#9,050 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github
Domain
security

Research direction

No repository file or test is mentioned. Start by reviewing the linked GHSA-4gfv-wg42-7jw5 advisory and checking its publication status in the GitHub Advisory Database; the issue is done when CVE-2026-62167 is reflected there or its status is explained.

Written by the indexing model from the issue text.

Description

I understand there may currently be a high volume of CVE submissions being processed. I’m following up on CVE-2026-62167, which has been assigned and published in the repository ( GHSA-4gfv-wg42-7jw5 ) but is still not reflected in the GitHub Advisory Database.

I’d appreciate it if you could check on its publication status.

Thank you!

Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 18h
Merged PRs (30d)
48

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/advisory-database

All issues in github/advisory-database

Similar issues

More Security issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.