Third-party vulnerability disclosure policy
How SEQ SIA (OffSeq) reports vulnerabilities it discovers in other vendors' products, and when it publishes them. To report a vulnerability in OffSeq's own systems, use our programme on the CERT.LV platform, opens in a new tab instead.
Version 1.0 · 14 November 2026
On this page
01
Scope
This policy covers vulnerabilities OffSeq discovers in software, hardware and services made by others: through independent research, through our honeypot and threat-intelligence work, and, with the client's consent, during client engagements.
It does not cover weaknesses specific to one organisation's environment, such as misconfigurations or custom software that was never publicly available. Those are reported to the owner only.
02
Findings from client engagements
When a client engagement uncovers a previously unknown vulnerability in a third-party product, we report it to the vendor only where the client has agreed to this in the engagement contract. Every report and advisory is anonymised: it describes the product flaw and never names the client or contains anything from their environment.
Clients are informed before we contact the vendor and before we publish, and may request a limited delay. Where Latvian law requires a vulnerability to be reported to CERT.LV, we report it and follow CERT.LV's decision on disclosure.
03
Coordination
CERT.LV, the national CSIRT of Latvia, is our default coordinator, and most of our disclosures to date were reported to it or through it. For vendors elsewhere we work with the relevant national CSIRT, the vendor's own security team or its CVE Numbering Authority.
04
Contacting the vendor
We look for a security contact in the vendor's security.txt, its security or PSIRT pages, the CVE List of Partners and through CERT.LV. The first message asks for a secure channel before technical details are shared; our OpenPGP key is available for encrypted replies.
The report includes the affected product and versions, a description of the flaw and its impact, steps to reproduce, and a proposed severity rating (CVSS).
If the vendor does not reply, we try again after 7 days and after a further 14 days, through another channel where one exists. If there is still no reply, we hand the case to CERT.LV or the relevant national CSIRT.
05
Timeline
We publish 90 days after first contacting the vendor, or earlier once a fix or mitigation is available and the vendor agrees.
If the vendor is working on a fix and needs more time, we extend the deadline by agreement, normally by no more than 30 days.
We may publish earlier, with whatever mitigation advice is available, if the vulnerability is being exploited in the wild, if details are already public, or if the vendor fixes it without telling its users.
06
CVE IDs
Every vulnerability we publish in a publicly available product gets a CVE ID. Where the vendor, an upstream project or its code host (such as GitHub) is a CVE Numbering Authority, it assigns the ID. Otherwise the ID currently comes from the coordinating CNA, usually ENISA. How we handle CVE IDs sets out the process in full.
07
Publication
Advisories are published on our advisories page and stay at a stable address. Each one names the CVE ID, vendor, product, affected and fixed versions, the weakness type (CWE), a CVSS rating, the fix or workaround, credit and the timeline of contact with the vendor.
The advisory is public before or at the same time as the CVE record. Exploit code is withheld while users cannot yet patch.
Advisory text may be freely reproduced, including in CVE records and vulnerability databases; a link to the original is appreciated.
08
Contact
Questions about this policy or about a disclosure in progress: security@offseq.com, encrypted with our OpenPGP key (fingerprint 16C6 FDFC C1EC 7417 EA1B 684D 11EC 34BA E0AB 46DA). We acknowledge messages within 3 business days.
09
References
This policy follows ISO/IEC 29147 (vulnerability disclosure) and the CVE Program CNA Operational Rules, opens in a new tab. It is reviewed yearly.