Embargo Policy

In accordance with our submission policy we handle all vulnerability reports and submissions with the highest level of confidence. This means that we do not share any details with 3rd parties without a reason, co-ordination with the submitter or the affected vendor. Therefore, submits may remain in an embargo state for several weeks until the processing has been finished. The main reasons for a delayed vulnerability handling are:

  • Long vulnerability moderation queue delays processing capabilities
  • Co-ordination with the affected vendor
  • Co-ordination with an intermediate partner (e.g. another CNA or MITRE)
  • Technical verification of the claims are pending
  • Legal analysis of issue and dependencies are pending
  • Agreement upon an extended embargo got established (e.g. vendor is preparing official patch)
The status of a vulnerability submit is shown in the submit itself. And a detailed status for your own submits is listed in your online cockpit. We do not answer any questions regarding the processing status. You will be informed within the submit or via email about a new status of your submit.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Actualizado: 2026-03-22 por VulDB Documentation Team

Do you know our Splunk app?

Download it now for free!

◂ AnteriorVisión De ConjuntoPróximo ▸