Coordinated vulnerability disclosure under the Cyber Resilience Act
5 min read
Vulnerabilities are often found by others: researchers, customers or partners. The Cyber Resilience Act therefore requires manufacturers to accept reports from outside, handle them in an orderly way and publish information on fixed vulnerabilities. This guide summarises what Annex I, Part II and Article 13 lay down – and how this differs from the reporting obligation under Article 14.
What it is about
A vulnerability is a weakness, susceptibility or flaw of a product with digital elements that can be exploited by a cyber threat (Art. 3(40)). When placing a product on the market, and for the support period, manufacturers ensure that vulnerabilities of the product, including its components, are handled effectively and in accordance with Annex I, Part II (Art. 13(8)).
Annex I, Part II lists eight requirements. For handling reports from outside, these matter most: a policy on coordinated vulnerability disclosure (point 5), a contact address for reports (point 6) and public disclosure of fixed vulnerabilities (point 4).
These obligations apply from 11 December 2027. Only the reporting obligation under Article 14 applies earlier, from 11 September 2026 (Art. 71(2)).
Source: Art. 3(40) CRA · Art. 13(8) CRA · Annex I, Part II CRA · Art. 71(2) CRA
Policy on coordinated vulnerability disclosure
Manufacturers must put in place and enforce a policy on coordinated vulnerability disclosure (Annex I, Part II, point 5). Recital 76 explains what it should look like:
- It facilitates reporting by individuals or entities – directly to the manufacturer or indirectly via the CSIRT designated as coordinator, anonymously where requested.
- It specifies a structured process: the manufacturer can diagnose and remedy the vulnerability before details are disclosed to third parties or the public.
- Manufacturers should consider publishing their security policies in machine-readable format.
- Programmes offering recognition and compensation to reporters (‘bug bounty programmes’) may form part of the policy. The Regulation does not make them mandatory.
If a manufacturer limits security updates to the latest version of a software product, the policy still applies – for all subsequent substantially modified versions (Recital 40).
Source: Annex I, Part II, point 5 CRA · Recital 76 CRA · Recital 40 CRA
Point of contact for reports
- Manufacturers take measures to facilitate the sharing of information about potential vulnerabilities in the product and in third-party components contained in it. This includes providing a contact address for reporting vulnerabilities discovered (Annex I, Part II, point 6).
- They designate a single point of contact that lets users communicate with them directly and rapidly – including to report vulnerabilities. It must be easily identifiable. Users must be able to choose their preferred means of communication; automated tools alone are not enough (Art. 13(17)).
- The information and instructions to the user state the single point of contact for reporting vulnerabilities and where the policy on coordinated vulnerability disclosure can be found (Annex II, point 2).
Source: Annex I, Part II, point 6 CRA · Art. 13(17) CRA · Annex II, point 2 CRA
Passing on vulnerabilities in components
If the manufacturer identifies a vulnerability in an integrated component – including an open-source component – it reports it to the person or entity manufacturing or maintaining the component. It also addresses and remediates the vulnerability in accordance with Annex I, Part II. Where it has developed a software or hardware modification to fix it, it shares the relevant code or documentation, where appropriate in a machine-readable format (Art. 13(6)).
The vulnerability handling obligations apply to the product in its entirety, including all integrated components (Recital 34).
Source: Art. 13(6) CRA · Recital 34 CRA
Publishing fixed vulnerabilities
Once a security update has been made available, the manufacturer shares and publicly discloses information about the fixed vulnerabilities (Annex I, Part II, point 4). This includes:
- a description of the vulnerabilities,
- information allowing users to identify the affected product,
- the impacts and severity of the vulnerabilities,
- clear and accessible information helping users to remediate the vulnerabilities.
Delay only in duly justified cases: where the manufacturer considers the security risks of publication to outweigh the security benefits, it may delay publication until users have been given the possibility to apply the patch (Annex I, Part II, point 4).
Updates are distributed via secure mechanisms so that vulnerabilities are fixed or mitigated in a timely manner – for security updates, automatically where applicable (point 7). Security updates are disseminated without delay and, as a rule, free of charge, accompanied by advisory messages on potential action (point 8).
How this differs from the reporting obligation under Article 14
Coordinated disclosure covers all vulnerabilities. The reporting obligation under Article 14 covers only actively exploited vulnerabilities: there is reliable evidence that a malicious actor has exploited the vulnerability in a system without permission of the system owner (Art. 3(42)). The manufacturer notifies such vulnerabilities via the single reporting platform to the CSIRT designated as coordinator and to ENISA (Art. 14(1)) and informs the impacted users (Art. 14(8)).
If a reported vulnerability is being exploited, both tracks run in parallel. In exceptional circumstances, an ongoing coordinated vulnerability disclosure procedure can be a reason for the CSIRT to delay dissemination of a notification to other CSIRTs (Recital 70). In addition, manufacturers and other persons may notify any vulnerability on a voluntary basis to a CSIRT designated as coordinator or to ENISA (Art. 15(1)).
Source: Art. 3(42) CRA · Art. 14(1), (8) CRA · Recital 70 CRA · Art. 15(1) CRA
In practice
The following points are our recommendations, not requirements of the Regulation:
- Publish the policy on coordinated vulnerability disclosure as a page on your website: how to report, what reporters can expect, timeframes, how publication is handled.
- Place a security.txt file under /.well-known/ in line with RFC 9116. It names the contact address (Contact field, mandatory) and points to the policy (Policy field). This fits the suggestion in Recital 76 to publish security policies in machine-readable format.
- Offer a second reporting channel besides email, such as a form – Art. 13(17) requires a choice of means of communication.
- Publish fixed vulnerabilities as security advisories, ideally also in machine-readable form, for example in the CSAF 2.0 format.
- Assign responsibilities: who receives reports, who assesses them, who informs the maintainers of affected components?
- Check every report immediately for active exploitation – if so, the Article 14 deadlines apply.
- Tools exist for reporting portals, security.txt and advisories; a well-rehearsed process matters more than the tool.
Related guides
- Reporting obligationsCyber Resilience Act: reporting under Art. 14, step by step7 min read
- Product and evidenceWhat is an SBOM? Obligations under the Cyber Resilience Act3 min read
- Product and evidenceSupport period under the Cyber Resilience Act: at least five years?3 min read
- Reporting obligationsSetting up access to ENISA’s single reporting platform4 min read
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 3, 13(6), (8), (17), Art. 14, 15, 71, Annex I, Part II, Annex II, Recitals 34, 40, 70, 76 (EUR-Lex, Official Journal)
- RFC 9116: A File Format to Aid in Security Vulnerability Disclosure (security.txt)
- OASIS Common Security Advisory Framework (CSAF) Version 2.0
First published 6 Nov 2026, last updated 6 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.