Pending CVE Assignment for Published Security Advisory (GHSA-4x92-9hqx-5f58) #213345
Replies: 1 comment 1 reply
|
What you're seeing is expected behaviour, not a failed submission. Publishing a GHSA and assigning a CVE are two separate steps, and the label on a published advisory can stay at "No known CVE" while GitHub's CNA queue works through the request. How the process actually worksGitHub is a CVE Numbering Authority for open-source projects hosted on GitHub. The flow is:
The docs say GitHub "usually reviews the request within 72 hours", but there is a documented backlog. In discussion #205706 GitHub staff said in September 2026 that, due to a large increase in CVE requests across the industry, they were processing records in order with roughly a five-week turnaround — and reporters in #210051 are seeing considerably longer. That second thread is a good one to follow for current status; it tracks exactly this symptom across several advisories. So "published GHSA, no CVE yet" = pending, not rejected. The GHSA ID is a perfectly citable identifier in the meantime; security scanners that support GHSA will pick it up. What you can do depends on your roleIf you reported the vulnerability but are not a maintainer, there is very little you can do directly. Only users with admin permission on the advisory can request a CVE or chase it. Reach out to the maintainer of If you are the maintainer / advisory admin, check it like this:
Do not re-submit the request. Re-requesting does not move it forward and can create duplicate work for the CNA. When to escalateIf the advisory is well past the stated turnaround, the maintainer can open one Support ticket at support.github.com/contact using the security-advisory/CVE category, listing the GHSA ID and the original request date. The community thread specifically advises against opening a ticket per advisory just to chase the queue. If you cannot wait at all, other CNAs (MITRE via cveform.mitre.org, or CERT/CC) can assign CVEs to open-source projects under their scope. Coordinate with the maintainer before doing that — two CNAs assigning the same vulnerability is a mess, and GitHub cannot assign a CVE to a project already covered by another CNA. Practical advice while you waitPublish the fix and the advisory now; don't hold a release for the CVE number. Put the GHSA ID in your release notes and changelog. Once GitHub assigns the CVE, it appears automatically on the advisory page and propagates to NVD in due course — no further action from you. Primary sources: About repository security advisories and Publishing a repository security advisory → Requesting a CVE identification number. More security write-ups on my GitHub if useful: https://github.com/P-r-e-m-i-u-m |
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Other
Body
Hello GitHub Community,
I am seeking guidance regarding a pending CVE assignment for a security vulnerability I reported.
The vulnerability has already been accepted and published as a GitHub Security Advisory.
Advisory details:
GHSA ID: GHSA-4x92-9hqx-5f58
Repository: sourcentis/mercator
Vulnerability: Privilege Escalation – Improper Privilege Management
Severity: High
Affected versions: <= 2026.10.09
Patched version: 2026.10.10
Advisory publication date: October 10, 2026
CVE request date: October 10, 2026
CVE status: Pending assignment
The repository maintainer requested a CVE assignment on October 10, 2026. However, the advisory still does not have an assigned CVE identifier.
I understand that CVE assignment processing times may vary, but I would appreciate clarification from anyone familiar with GitHub's CVE assignment process.
All reactions