You found a vulnerability in an open-source project, and naturally, you'd like a CVE assigned to it. But where should you report it?

With the growing number of vulnerability reports, long assignment queues, and sometimes unresponsive vendors, getting a CVE can be surprisingly frustrating.

I've learned that spending a few minutes checking how a project has handled previous CVEs can save weeks of waiting. Here's the process I usually follow before submitting a vulnerability.

1. Check who assigned the project's latest CVEs

Start by searching for the project's most recent CVEs on CVE.org.

Each record has an Assigning CNA field. A CNA (CVE Numbering Authority) is an organization authorized to assign CVE identifiers, such as a software vendor, GitHub, or a vulnerability coordination organization.

Look through the latest few CVEs and check which CNA assigned them.

You can also simply ask an AI assistant with web access to investigate the project's CVE history, current CNA, and reporting options, then verify the findings against official sources.

Once you know who's been assigning the project's CVEs, you can decide where to report yours.

2. If the vendor has its own CNA

If the vendor is a CNA and has been actively assigning CVEs, I'd generally recommend reporting directly through its security disclosure channel.

You can check whether a vendor is a CNA and what products it covers in the official CNA directory.

Pay attention to the dates of previous assignments. A vendor that actively assigns CVEs is usually a more promising option than one whose last assignment was years ago.

3. If GitHub assigned the previous CVEs

GitHub is also a CNA and can assign CVEs through repository security advisories.

If the project has private vulnerability reporting enabled, you can submit your finding through its Security → Advisories section. The maintainers can then create an advisory, request a CVE from GitHub, and credit you as the finder.

The process is convenient when maintainers cooperate, although the actual assignment can take a while.

GitHub has acknowledged a significant increase in CVE requests. In September 2026, its staff reported a turnaround of approximately five weeks, and some researchers have experienced considerably longer delays.

I'd still consider this route for projects that actively use GitHub advisories, but it's worth keeping the backlog in mind.

More information is available in GitHub's documentation.

4. If neither looks promising, consider VulnCheck

One option that has helped me a lot is VulnCheck.

VulnCheck is a CNA that accepts vulnerability reports directly from independent researchers and can coordinate the entire disclosure process on your behalf.

I've personally had a really good experience with them. They've been fast, responsive, and easy to communicate with, which makes the process much more pleasant.

You can submit a report through their reporting form or email disclosure@vulncheck.com.

When submitting, you can choose to let VulnCheck handle vendor communication and disclosure coordination. They'll contact the maintainers, help validate the finding, coordinate CVE assignment, and manage the disclosure timeline.

This is especially useful when the vendor is unresponsive, which is unfortunately something researchers encounter quite often.

What happens if the vendor never responds?

VulnCheck follows a 120-day coordinated disclosure policy. The vendor gets up to 120 days to fix the vulnerability or publish an advisory. If that doesn't happen, VulnCheck's policy provides for publishing its own advisory, even without the vendor's cooperation.

For eligible vulnerabilities, VulnCheck can assign the CVE itself or coordinate with the appropriate CNA. The 120-day deadline applies to disclosure rather than guaranteeing automatic CVE assignment on day 120.

And you often won't need to wait nearly that long.

According to VulnCheck, its average time from initial report to public disclosure for coordinated cases is approximately 48 days, and already-public vulnerabilities can sometimes receive CVE assignments within hours.

Its analysts also aim to respond within one business day.

For me, having someone handle the communication, coordination, and CVE process is a huge advantage, particularly when maintainers aren't responding.

You can read their disclosure policy for the full details.

5. What about MITRE?

MITRE still operates a CNA of Last Resort and assigns CVEs for eligible vulnerabilities.

However, with the current volume of submissions and longer processing times, I wouldn't make it my first choice when another appropriate CNA is available.

If the vendor has an active CNA, I'd generally prefer that. Otherwise, I'd investigate GitHub or VulnCheck before considering MITRE's CNA-LR request process.

Final thoughts

My usual process is to check the project's latest CVEs, identify who's been assigning them, and choose the reporting route accordingly.

If the vendor has an active CNA, I'll generally start there. If the project uses GitHub advisories, that's another option, although the current queues are worth considering.

And when neither route looks particularly promising, VulnCheck has been a great alternative in my experience.

Hopefully, this helps someone avoid a few weeks of unanswered emails :)