root@hckrt: ~# cat cvd-guide.txt
Coordinated Vulnerability Disclosure (CVD)
From the first report to a coordinated release, give researchers and your team a clear plan for what happens next.
- Receive the report
A trusted route to the right team.
- Validate and prioritize
Evidence, impact, and an owner.
- Agree a plan
Clear dates. Consistent updates.
- Remediate and verify
A fix connected to the finding.
- Coordinate disclosure
Prepare the people who need to act.
One report. One owner. A clear next update.
Start with a shared understanding
What is coordinated vulnerability disclosure?
Coordinated Vulnerability Disclosure (CVD) is the process through which researchers, affected organizations, and sometimes a coordinator work together to understand a vulnerability, address its impact, and plan how information reaches the people who need it.
A Vulnerability Disclosure Policy (VDP), also commonly called a Responsible Disclosure Policy (RDP), sets the reporting rules and expectations. CVD puts the handling and communication around an individual finding into practice.
The CVD process
A clear path from report to resolution.
Prepare the channel before the first report arrives, then keep evidence, decisions, and communication connected through every stage.
Prepare the reporting route
Publish a policy with asset scope, reporting instructions, secure contact options, and expectations for researchers. Assign an internal owner and a backup contact. Make sure incoming reports can reach the people who can investigate and authorize the next step.
Receive and acknowledge
Give the researcher a report reference, a contact, and a next update date. Request affected products or versions, reproduction steps, and supporting evidence. Keep sensitive material in the agreed channel and ask for only the information needed to understand the issue.
Validate and prioritize
Check scope, reproduce the behavior where authorized, and assess severity with the affected team. Record missing evidence, duplicates, and dependencies. Distinguish a confirmed vulnerability from a report still under review, and route urgent findings to the appropriate response owner.
Agree the coordination plan
Identify the remediation owner, affected vendors or downstream users, and a proposed disclosure date. Agree how often updates will be shared, who can approve changes, and how to escalate a stalled conversation. Record the plan so each party understands its responsibilities.
Remediate and verify
The product or service owner implements a fix or mitigation and checks the affected versions. Agree any researcher retesting in advance, including access and scope. Record what was verified, what remains open, and how users can apply the recommended action.
Coordinate release and learn
Align the fix, advisory, affected-version information, and user notifications with the parties involved. Agree researcher credit and the technical detail to publish. Where a CVE is appropriate, coordinate with the relevant CNA. Close the report with a clear outcome and review what the process can improve.
Connect incoming reports to vulnerability triage and report validation, with CVE coordination where appropriate.
Response and disclosure timelines
Set expectations. Keep them current.
Choose targets your team can meet and distinguish acknowledgement, assessment, remediation, and public disclosure. Each milestone needs its own owner and update.
Example planning cadence
Illustrative targets to discuss with your team. Publish commitments you can meet; Hackrate service response times are agreed separately.
Acknowledge receipt
Example targetWithin 2 business days
Report reference, point of contact, and when the researcher will next hear from you.
Share an initial assessment
Example targetWithin 5 business days
Scope, validation status, missing information, and any urgent escalation.
Keep progress visible
Example targetEvery 7 calendar days
Work completed, blockers, changed risks, and the next update date, even when a fix is still in progress.
Set a remediation target
Example targetAgree after triage
Engineering ownership, affected versions, interim mitigations, and the verification plan.
Coordinate public disclosure
Example targetAgree and review the date
Fix and advisory readiness, downstream notifications, researcher credit, and any changes to the release plan.
Review the plan when the risk changes.
Fix complexity, affected suppliers, and downstream deployment can change the schedule. Evidence of active exploitation or a public leak calls for urgent review, mitigation, and communication. Explain delays, propose a revised date, and agree the next update. Remediation and public disclosure may need different dates.
Read CERT/CC's disclosure timing guidanceRoles and responsibilities
Shared work. Clear ownership.
Agree who investigates, who fixes, who communicates, and who approves release. A coordinator helps connect the work while the affected organization retains its decisions.
Security researcher
- Provide reproducible evidence and affected-version details.
- Follow the published scope and minimize access to sensitive data.
- Discuss further testing, disclosure timing, and credit preferences.
Product or service owner
- Assign a response owner, assess impact, and authorize investigation.
- Implement and verify remediation or mitigations.
- Own risk decisions, release approval, and notifications to affected users.
Coordinator or managed partner
- Keep the report, contacts, decisions, and next steps connected.
- Support validation, routing, and researcher communication as agreed.
- Help align affected parties and escalate communication gaps.
Hackrate's managed VDP supports report intake, validation, and researcher communication. Remediation and disclosure decisions remain with your organization, with responsibilities defined in the agreed service.
Researcher communication
Keep the researcher in the loop.
A useful update tells the researcher what you know, what happens next, and when to expect another message. Keep sensitive details in the agreed reporting channel.
Acknowledge with a next step
Confirm receipt and give a reference, a contact, and a next update date. Keep acknowledgement separate from acceptance of the finding.
Ask focused questions
Explain which reproduction detail or version information is missing. Request redacted evidence and keep any additional testing within agreed scope.
Make changes visible
Share progress and blockers on the agreed cadence. If the plan changes, explain why and give a revised target and next check-in.
Close the loop clearly
Explain the outcome, including duplicates or findings outside scope. Agree credit, provide published advisory links where relevant, and record any remaining work.
If communication stalls, try the agreed backup contact, record the attempts, and consider an appropriate coordinator. Keep the discussion factual and revisit the plan openly when risks change.
Continue reading
Guidance behind the process.
Use these resources alongside your organization's published policy and agreed response procedures.
- CERT/CC: disclosure timing
Factors that affect coordination and release decisions.
- NCSC: Vulnerability Disclosure Toolkit
Reporting channels, policies, and response preparation.
- OWASP: Vulnerability Disclosure Cheat Sheet
Practical guidance for researchers and organizations.
- OpenSSF: researcher coordination guidance
Sharing useful evidence and coordinating with maintainers.
Put coordinated disclosure into practice
Turn your policy into a working process.
Connect a trusted reporting channel with expert validation and researcher communication through Hackrate's managed vulnerability disclosure service.
Hackrate
Our platform helps companies to identify software vulnerabilities in a cost-efficient way. It provides a secure and centralized view of ethical hacking projects for your company.
US Patent Applied for HackGATE #63/645,845
Products
From the Blog
-
Hackrate Ranked 1st in Hungary and 22nd Globally at Hack The Box’s Global Cyber Skills Benchmark 2026
May 29 • 13 min read
-
Press release: Hackrate becomes Hungary’s first CVE Numbering Authority
Jan 13 • 5 min read ★
-
Let 2026 be the year bug bounty becomes part of how you build and operate
Jan 05 • 4 min read
