Cyber Resilience Act: reporting under Art. 14, step by step
As of 7 min read
Article 14 of the Cyber Resilience Act has applied since 11 September 2026. Manufacturers must report actively exploited vulnerabilities and severe incidents within staged deadlines – via ENISA’s single reporting platform. This guide walks through the obligation step by step.
From when and for which products
Regulation (EU) 2024/2847 generally applies from 11 December 2027. Under Art. 71(2), Article 14 already applies from 11 September 2026.
Under Art. 69(3), the reporting obligations also cover products with digital elements placed on the market before 11 December 2027. Anyone who has products within the scope on the EU market today is therefore already subject to the reporting obligations – even though the other requirements do not yet apply.
According to the Commission guidelines (C/2026/6013, point 217), there is no retroactive reporting if the exploitation was already known before 11 September 2026. If only the vulnerability was known before and the exploitation becomes known afterwards, the obligation applies. The guidelines are not binding.
Source: Art. 71(2) CRA · Art. 69(3) CRA · Commission guidance C/2026/6013, point 217
What must be reported
Article 14 has two triggers for reporting:
- Actively exploited vulnerabilities (Art. 14(1)): vulnerabilities for which there is reliable evidence that a malicious actor has exploited them in a system without permission of the system owner (definition in Art. 3(42)).
- Severe incidents having an impact on the security of the product (Art. 14(3)).
Under Art. 14(5), an incident is severe if it negatively affects or is capable of negatively affecting the ability of the product to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions – or if it has led or is capable of leading to the introduction or execution of malicious code in the product or in the network and information systems of a user.
A vulnerability that is merely known but not exploited does not fall under Article 14. It can be reported voluntarily under Article 15 – as can cyber threats, incidents and near misses. According to its FAQ (No 27, as of 15 October 2026), however, ENISA’s single reporting platform does not yet accept voluntary reports.
According to the Commission guidelines (point 218), vulnerabilities in third-party components only have to be reported if they are exploitable and have been exploited in the manufacturer’s own product. The obligation under Art. 13(6) to report the vulnerability to the manufacturer or maintainer of the component applies regardless.
Source: Art. 3(42) CRA · Art. 14(1), (3), (5) CRA · Art. 15 CRA · Commission guidance C/2026/6013, point 218 · ENISA FAQ on the Single Reporting Platform, No 27
Step 1: Record when you became aware
All deadlines run from the moment the manufacturer becomes aware. According to the Commission guidelines (point 213), the manufacturer is aware when, after an initial assessment, it has a reasonable degree of certainty that a reportable case exists.
Record this moment with date, time and time zone – together with the information that triggered it. It determines all further deadlines and will be the first question if authorities follow up.
Source: Art. 14(2), (4) CRA · Commission guidance C/2026/6013, point 213
Step 2: Determine the competent CSIRT
Reports go simultaneously to the CSIRT designated as coordinator and to ENISA, via the single reporting platform under Article 16 (Art. 14(1)). Which CSIRT is competent is set out in Art. 14(7):
- the CSIRT of the Member State in which the manufacturer has its main establishment – that is, where the decisions related to cybersecurity are predominantly taken;
- if that cannot be determined: the Member State of the establishment with the highest number of employees in the Union;
- without a main establishment in the Union, in this order: the Member State of the authorised representative acting on behalf of the manufacturer for the highest number of its products; of the importer placing the highest number of products on the market; of the distributor making the highest number of products available – otherwise the Member State with the highest number of users.
For manufacturers established in Germany, the CSIRT designated as coordinator is CERT-Bund at the BSI (ENISA list, as of 10 September 2026). According to the ENISA FAQ (No 18), choosing the wrong CSIRT on the platform risks the report being declared invalid and having to be resubmitted.
Source: Art. 14(1), (7) CRA · ENISA: list of CSIRTs designated as coordinators · ENISA FAQ on the Single Reporting Platform, No 18
Step 3: Deadlines for actively exploited vulnerabilities
Art. 14(2) provides for three stages:
- Early warning notification – without undue delay and in any event within 24 hours of becoming aware. Where applicable, it names the Member States on whose territory the manufacturer is aware that the product has been made available.
- Vulnerability notification – without undue delay and in any event within 72 hours of becoming aware, unless already provided. Content: general information about the product, the general nature of the exploit and of the vulnerability, any corrective or mitigating measures taken, measures users can take, and, where applicable, how sensitive the information is.
- Final report – no later than 14 days after a corrective or mitigating measure is available. Content: a description of the vulnerability including its severity and impact, where available information concerning the malicious actor, and details about the security update or other corrective measures.
The 14-day deadline does not start when you become aware, but only once a correction is available. Until then, the case remains open.
Source: Art. 14(2) CRA
Step 4: Deadlines for severe incidents
Under Art. 14(4), severe incidents also follow three stages:
- Early warning notification – without undue delay and in any event within 24 hours of becoming aware. It must at least indicate whether the incident is suspected of being caused by unlawful or malicious acts; where applicable, also the Member States on whose territory the product has been made available.
- Incident notification – without undue delay and in any event within 72 hours of becoming aware, unless already provided. Content: the nature of the incident, an initial assessment, any corrective or mitigating measures taken, measures for users and, where applicable, how sensitive the information is.
- Final report – within one month of the incident notification. Content: a detailed description including severity and impact, the type of threat or root cause that is likely to have triggered the incident, and applied and ongoing mitigation measures.
Art. 14(6) only requires an intermediate report if the CSIRT designated as coordinator requests it – in both types of case.
Source: Art. 14(4), (6) CRA
Step 5: Submit via ENISA’s single reporting platform
Reports are submitted via ENISA’s Single Reporting Platform (SRP), in operation since 11 September 2026. According to the ENISA FAQ (as of 15 October 2026):
- Sign-in via a personal EU Login account with multi-factor authentication.
- Per manufacturer, one primary and up to 20 further representatives (“Assigned Representatives”); the CSIRT designated as coordinator confirms the link to the manufacturer.
- The platform is only available in English and has no interface (API) in its first release – reports are entered manually.
- If the platform is unavailable, ENISA advises waiting; if it is urgent, contact the CSIRT directly and submit the report on the platform afterwards.
- The platform’s 72-hour counter currently shows a deadline 48 hours after the early warning notification, not 72 hours after becoming aware. The statutory deadline remains decisive.
Because the platform only works in English, it pays to prepare texts for the reports in English in advance. How to set up access is described in the guide “Setting up access to ENISA’s single reporting platform”.
Source: ENISA FAQ on the Single Reporting Platform, No 9, 15, 24, 25, 26
Step 6: Inform users
After becoming aware, the manufacturer informs the impacted users – and, where appropriate, all users – about the vulnerability or incident and, where necessary, about risk mitigation measures they can take; where appropriate in a structured, machine-readable format (Art. 14(8)). The wording does not set a fixed deadline for this.
If the manufacturer fails to inform users in a timely manner, the CSIRT designated as coordinator may provide the information itself where it considers this proportionate and necessary.
Source: Art. 14(8) CRA
What you should prepare now
- Determine the competent CSIRT and create EU Login accounts with multi-factor authentication for the people who report.
- Decide who reports within the company and who deputises – including at weekends.
- An up-to-date SBOM per product and version, so you can quickly see which products a vulnerability affects.
- Write down the procedure: who establishes awareness, how it is documented and who monitors the deadlines.
- A list of the Member States in which each product is made available – it already belongs in the early warning notification.
Source: Annex I, Part II, point 1 CRA
Related guides
- Product and evidenceCyber Resilience Act timeline: all key dates3 min read
- Reporting obligationsPHP2Shell and the Cyber Resilience Act: what manufacturers must do now6 min read
- Reporting obligationsSetting up access to ENISA’s single reporting platform4 min read
- Product and evidenceWhat is an SBOM? Obligations under the Cyber Resilience Act3 min read
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 3(42), Art. 14, 15, 69, 71 (EUR-Lex, Official Journal)
- Commission: guidance on the application of Regulation (EU) 2024/2847, C/2026/6013, OJ C, 17 Nov 2026
- ENISA: Single Reporting Platform – FAQ, as of 15 October 2026
- ENISA: list of CSIRTs designated as coordinators
Status of the Commission guidance: the Commission approved its content on 27 July 2026 (C(2026) 5252). On 17 November 2026 the guidance was published in the Official Journal as Communication C/2026/6013, in all official languages. According to our comparison, the point numbers have not changed. The guidance is not binding, but it shows how the Commission reads the Regulation (as of 11/2026).
First published 19 Oct 2026, last updated 18 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.