Regulation (EU) 2024/2847 · Article 13(8) & Annex I Part II(5)

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

  1. 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).
  2. Annex I Part II(6) requires manufacturers to publish a contact address for reporting vulnerabilities in their products and third-party components.
  3. 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.
  4. 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.

DimensionCVD under Article 13(8) & Annex I Part IIReporting under Article 14
Legal basisArticle 13(8), Annex I Part II(5) and (6)Article 14 and Article 16
TriggerAny potential vulnerability reported by a researcher, user, or partnerActively exploited vulnerability or severe security incident
RecipientsExternal reporters, users, and downstream integratorsENISA and the coordinating national CSIRT simultaneously
Statutory deadlinesRemediate without delay under Annex I Part II(2). CVD Portal uses 48 hours as an optional acknowledgment target24h early warning, 72h full notification, and 14-day or 1-month final report
Application date (Article 71(2))11 December 202711 September 2026
Primary outputPublished CVD policy, security.txt contact, triage audit trail, and security advisoryNotifications 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. 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. 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. 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. 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. 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. 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. 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.

Flow diagram of the disclosure portal lifecycle. A security researcher submits a report, which enters the New state. It moves to Acknowledged, then In Progress, then Resolved, and the chain ends in a published advisory. In Progress can also close as Dismissed. A 48 hour acknowledgment target sits below the New state and is a portal default a company can configure. Below Acknowledged sits the BSI TR-03183-3 expectation of a person-written reply within five working days.
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.

Frequently asked questions on CVD and the CRA

What is coordinated vulnerability disclosure?
Coordinated vulnerability disclosure (CVD) is the process by which a security researcher reports a flaw to the affected vendor privately, the vendor remediates the flaw, and the parties publish information about the vulnerability and the fix on a coordinated timeline. It contrasts with full disclosure (publish immediately) and non-disclosure (keep secret). CVD is the international norm under ISO/IEC 29147 and the basis for the EU CRA's Article 13 obligation.
Is CVD mandatory under the EU CRA?
Yes for manufacturers of products with digital elements. Annex I Part II(5) of Regulation (EU) 2024/2847, through Article 13(8), requires every such manufacturer to have a policy on coordinated vulnerability disclosure from 11 December 2027. Annex I Part II(6) also requires a public contact address. Article 14 adds reporting obligations for actively exploited vulnerabilities and severe incidents.
When do the CRA CVD requirements apply?
Under Article 71(2), Article 13 and Annex I apply in full from 11 December 2027. However, Article 14 reporting of actively exploited vulnerabilities has applied since 11 September 2026, so manufacturers need an active disclosure channel now to catch incoming reports.
How does CVD under Article 13 relate to Article 14 reporting?
Article 13 and Annex I Part II govern how manufacturers receive, handle, and disclose vulnerabilities with researchers and users. Article 14 governs mandatory notifications to ENISA and the coordinating CSIRT when a vulnerability is actively exploited or causes a severe incident.
What is the difference between CVD and a VDP?
CVD is the process. A VDP (Vulnerability Disclosure Programme or Platform) is the operational implementation. You publish a CVD policy, you operate a VDP. In EU regulatory and standards documents (ISO/IEC 29147, ENISA guidance) the term CVD is more common, while US security industry parlance uses VDP. The substance is the same.
How long does the coordinated disclosure period last?
A common default is 90 days from report to public disclosure, the timeline Project Zero uses. CERT/CC uses 45 days. The exact period is negotiable between researcher and vendor. Active exploitation typically shortens it, while complex remediation may justify extension. Document the agreed timeline in writing.
What if the researcher does not agree to coordination?
Acknowledge the report regardless. Make the vendor's position clear in the published policy: the vendor will treat good-faith research with safe-harbour protections, but cannot prevent a researcher from publishing on their own timeline. The reputational and legal cost of suing security researchers is almost always higher than the cost of accelerated remediation.
What is a CSAF advisory?
CSAF 2.0 (Common Security Advisory Framework) is a machine-readable JSON format for security advisories. It allows downstream consumers (SBOM tooling, vulnerability management platforms, asset inventories) to ingest vendor advisories automatically. Annex I Part II(4) requires manufacturers to share information on fixed vulnerabilities when updates ship, and CSAF 2.0 is the format the rest of the industry expects.

Official guidance and primary sources

Primary EU legal texts, ENISA guidance, and authoritative CVD resources from national cyber security agencies.

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.