How we handle CVE IDs
OffSeq is applying to become a CVE Numbering Authority (CNA) under the ENISA Root, opens in a new tab. This page sets out how we will assign CVE IDs and publish CVE records once authorised, and how CVE IDs for our findings are obtained until then.
Version 1.0 · 14 November 2026
On this page
01
Status
Until our CNA authorisation is confirmed, CVE IDs for vulnerabilities we find are assigned by the vendor's CNA or by ENISA, as for all our published CVEs so far. Once authorised, our entry will appear in the CVE List of Partners, opens in a new tab.
02
Scope
Proposed scope: all OffSeq products, and vulnerabilities in third-party products discovered by OffSeq that are not in another CNA's scope.
OffSeq products are those on our solutions page, including Threat Radar, Mirage and Mirage Feed, Breach, Guard, Pulse and Veil, and our open-source tools such as threat-finder, opens in a new tab. Products that have reached end of life are treated the same as supported ones, and their records carry the “unsupported-when-assigned” tag. Records for flaws fixed entirely in a service we host carry the “exclusively-hosted-service” tag.
03
Can OffSeq assign a CVE ID for me?
Once we are authorised: yes, for a vulnerability in an OffSeq product. For other products we assign IDs only for vulnerabilities OffSeq discovered.
For anything else, contact the vendor's CNA (see the List of Partners, opens in a new tab), ENISA for vulnerabilities coordinated by an EU CSIRT, or MITRE as the CNA of Last Resort, opens in a new tab. Tell us if you have already asked another CNA, so the same vulnerability does not receive two IDs.
04
How we decide
We assign an ID when a flaw in a publicly available product is confirmed and will be disclosed. Each vulnerability that can be fixed independently gets its own ID; issues that share one fix share one ID.
If the vendor or an upstream project is a CNA, it gets the first opportunity to assign, and we do not assign IDs outside our scope. We make a good-faith effort to notify the vendor of every vulnerability before an ID is published.
If that CNA declines or does not reply within 72 hours, we ask ENISA as our Root to decide, or request the ID from the MITRE CNA of Last Resort.
05
From reservation to publication
We reserve the ID when we notify the vendor and pass it to the reporter. It stays reserved, with no details, during the embargo set by our disclosure policy.
On the agreed date our advisory is published on the advisories page first or at the same moment, and the CVE record follows within 24 hours, and never later than 72 hours.
We update the record when a fix becomes available or a material error is found, and reject any reserved ID that is not used.
06
What a CVE record contains
The vendor and product, affected and fixed versions, the weakness type (CWE), an English description, a link to the public advisory and, where useful, CVSS 4.0 and 3.1 ratings. Credit goes in the record's credits field, not in the description.
07
Contact
CVE requests and questions about a record: security@offseq.com, plain or encrypted with our OpenPGP key. Requests do not need an account or acceptance of any terms. We acknowledge within 3 business days.
08
Disputes
To dispute a CVE record we published, email security@offseq.com with the CVE ID, your reasoning and supporting evidence. We follow the CVE Record Dispute Policy, opens in a new tab: we acknowledge within 3 business days and decide within 5 business days of acknowledging, and the record is tagged “disputed” while a credible dispute is under review.
If you disagree with our decision, or a decision takes longer than 15 business days, you can escalate to ENISA as our Root at vuln@enisa.europa.eu, and from there to the MITRE Top-Level Root. Until we are authorised, disputes about records for our findings go to the CNA that assigned them.