Skip to content
ResilientX SecurityResearch Labs

03 Research area

Disclosure & CVEs

Vendor first, always: private reports to the vendor’s PSIRT, coordinated embargoes, CVE records through a CNA, and advisories with root cause and detection guidance once a fix ships.

01 Overview

A vulnerability report is a security-critical artefact. Where it goes, who can read it, how long the vendor has and how much detail is published decide whether the research protects users or arms attackers.

We run disclosure with the same rigour as the research: one owner per finding, a tracked timeline, and the vendor’s fix verified against the original proof of concept before anything is published.

02 Process

How a disclosure runs

  1. 01

    Private report

    Root cause, affected versions, a proof of concept and a CVSS v4.0 vector, delivered to the vendor’s PSIRT or security contact over a private channel.

  2. 02

    Coordination

    An agreed embargo and fix date, direct answers to the vendor’s engineers, and a retest of the patched build against the original PoC and its variants.

  3. 03

    CVE record

    A CVE ID from the vendor’s CNA or another appropriate CNA, with CWE classification and affected-product data that scanners and SBOM tooling can match.

  4. 04

    Advisory

    Published once a fix or mitigation ships: root cause, affected and fixed versions, detection guidance and the complete disclosure timeline.

03 Principles

What we hold ourselves to

Vendor first

Findings are shared only with the affected vendor until a fix or mitigation is available. We do not sell vulnerabilities or exploits.

Agreed timelines

A disclosure date agreed with the vendor up front, tracked from first contact, and publication only after the fix ships.

Machine-readable output

CVE records with CWE and CVSS data alongside every advisory, so defenders can automate detection and patch prioritisation.

Open to reports

The same rules apply in reverse: vulnerabilities in ResilientX Security products can be reported privately to our security team.

04 Report

Found a vulnerability in our products?

Report it privately to our security team. We acknowledge every report and keep you updated until it is fixed.

security@resilientx.com

05 Engage

Request an
engagement

Free for open-source products

Commission the Labs team for white-box or black-box research on a product, device or service you build or depend on: zero-day hunting, exploitability assessment or threat research. Tell us the target and we will scope the work with you.

Found a vulnerability in our products? Report it privately to security@resilientx.com · security.txt

What do you need? (optional)

By submitting you accept the privacy policy.