What is coordinated vulnerability disclosure (CVD) under the CRA?
Coordinated vulnerability disclosure (CVD) is a process where researchers report product flaws privately so manufacturers can fix reported flaws before publication. Under Regulation (EU) 2024/2847 (Cyber Resilience Act), Article 13(8) and Annex I Part II(5) require manufacturers to enforce a CVD policy from 11 December 2027, while operational intake supports Article 14 reporting active since 11 September 2026.
Last updated 14 November 2026
Key takeaways
- Regulation (EU) 2024/2847 requires every manufacturer of products with digital elements to put in place and enforce a coordinated vulnerability disclosure (CVD) policy under Annex I Part II(5), made binding by Article 13(8).
- Annex I Part II(6) requires manufacturers to publish a contact address for reporting vulnerabilities in their products and third-party components.
- Article 13 CVD duties apply in full from 11 December 2027, while Article 14 reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026.
- ISO/IEC 29147 sets the international disclosure standard, and CSAF 2.0 is the standard machine-readable format for security advisories.
How do CRA Article 13 CVD and Article 14 reporting compare?
Manufacturers often confuse coordinated vulnerability disclosure with authority incident reporting. Article 13 and Annex I Part II cover how you work with external reporters and users, while CRA Article 14 reporting obligations govern mandatory notifications to ENISA and national CSIRTs.
| Dimension | CVD under Article 13(8) & Annex I Part II | Reporting under Article 14 |
|---|---|---|
| Legal basis | Article 13(8), Annex I Part II(5) and (6) | Article 14 and Article 16 |
| Trigger | Any potential vulnerability reported by a researcher, user, or partner | Actively exploited vulnerability or severe security incident |
| Recipients | External reporters, users, and downstream integrators | ENISA and the coordinating national CSIRT simultaneously |
| Statutory deadlines | Remediate without delay under Annex I Part II(2). CVD Portal uses 48 hours as an optional acknowledgment target | 24h early warning, 72h full notification, and 14-day or 1-month final report |
| Application date (Article 71(2)) | 11 December 2027 | 11 September 2026 |
| Primary output | Published CVD policy, security.txt contact, triage audit trail, and security advisory | Notifications submitted through the ENISA Single Reporting Platform |
The three disclosure models
Full disclosure. The researcher publishes findings immediately, without coordinating with the vendor. It maximises public information and also maximises the exposure window before a patch exists.
Non-disclosure. The vulnerability is kept secret, often for offensive or grey-market use. From the outside, a vendor with no channel looks identical to a vendor with no security culture.
Coordinated disclosure. The researcher reports privately to the vendor, an agreed timeline is set, the remediation ships, and the advisory publishes alongside or shortly after. ISO/IEC 29147 codifies the practice, and CRA Article 13 makes it mandatory for manufacturers.
Seven steps to operate a CVD process under the CRA
The minimum operational set for a manufacturer selling into the EU under Article 13 of the Cyber Resilience Act, with Article 14 reporting at the end where applicable.
- 1
Publish a CVD policy
A short public document that describes scope, authorised testing methods, the reporting channel, your acknowledgment timeline, your remediation target, and a safe-harbour statement. Reference ISO/IEC 29147 for the framing. Under CRA Annex I Part II(5), which Article 13(8) makes binding, it is a legal duty from 11 December 2027 for every manufacturer that sells products with digital elements in the EU.
- 2
Set up a single point of contact
A monitored intake channel under your brand to satisfy Annex I Part II(6). A dedicated email address and a structured submission form on a hosted policy page are the minimum. Add the reporting address to your security.txt file at /.well-known/security.txt, which is the machine-readable half of the same contact.
- 3
Acknowledge within 48 hours
48 hours is the CVD Portal default, not a statutory deadline. BSI TR-03183-3 requires a simple response written by a person, never an automated reply, within five working days. Auto-acknowledge on receipt if you like, then assign a triage owner the same day and follow up in person.
- 4
Triage and assess severity
Confirm the vulnerability, determine severity (CVSS 3.1 or 4.0), check for duplicates, and decide on a remediation target date. Check whether there is evidence of active exploitation, because active exploitation starts the 24-hour Article 14 reporting clock.
- 5
Coordinate disclosure
Agree an embargo date with the reporter. The default norm is publication around the remediation release. Active exploitation may justify earlier disclosure. Pending CSIRT coordination may justify a longer window. Document the rationale either way.
- 6
Publish an advisory
Issue a security advisory once a security update is available, as required by Annex I Part II(4). Include affected versions and mitigation steps. CSAF 2.0 is the machine-readable industry standard. Credit the reporter unless they request anonymity.
- 7
Report to regulators where required
Under CRA Article 14, actively exploited vulnerabilities and severe incidents trigger a 24h early warning to the coordinator CSIRT and ENISA through the ENISA Single Reporting Platform, then a 72h notification and a final report. The final report is due 14 days after a fix for a vulnerability, or 1 month after the 72h notification for an incident. These duties apply from 11 September 2026.

Frequently asked questions on CVD and the CRA
What is coordinated vulnerability disclosure?
Is CVD mandatory under the EU CRA?
When do the CRA CVD requirements apply?
How does CVD under Article 13 relate to Article 14 reporting?
What is the difference between CVD and a VDP?
How long does the coordinated disclosure period last?
What if the researcher does not agree to coordination?
What is a CSAF advisory?
Official guidance and primary sources
Primary EU legal texts, ENISA guidance, and authoritative CVD resources from national cyber security agencies.
- Regulation (EU) 2024/2847 (Cyber Resilience Act) on EUR-Lex
Official legal text in the Official Journal of the European Union (CELEX:32024R2847), including Article 13(8), Article 14, Article 71(2), and Annex I Part II.
- ENISA Vulnerability Disclosure
The European Union Agency for Cybersecurity's reference hub on coordinated vulnerability disclosure policies, national CSIRT coordination, and EU practices.
- Establishing a Coordinated Vulnerability Disclosure Program to Work With Security Researchers
Joint guide from CISA, NSA, JPCERT/CC, NCSC-NL, and NCSC-UK (July 2026). Covers policy design, safe harbour, security.txt, CVE assignment, CSAF publication, and researcher recognition. Explicitly notes that the EU CRA requires suppliers to maintain a vulnerability disclosure policy.
- The NCSC Vulnerability Disclosure Toolkit
The UK National Cyber Security Centre's practical toolkit for setting up a disclosure process. Communication, policy, and security.txt in a compact package.
- FIRST Vulnerability Coordination SIG
The Forum of Incident Response and Security Teams' guidelines and practices for multi-party vulnerability coordination and disclosure, for cases involving several vendors or coordinators.
- CERT Guide to Coordinated Vulnerability Disclosure
Carnegie Mellon CERT/CC's comprehensive reference on CVD roles, phases, and edge cases, including public awareness and silent-fix pitfalls.
Published by Porta Regulus B.V. under CVD Portal editorial policy. Related pages: CRA-compliant CVD policy template, VDP buyer guide, and security.txt for CRA Article 13.
Stand up a CRA-ready CVD process in under an hour
CVD Portal supports all seven steps: published policy, hosted intake, acknowledgment target, triage, coordinated timeline, CSAF advisory, and the SRP-ready Article 14 package.