CRA Reporting Obligation: Deadlines, Content and Reporting Channel
Since 11 September 2026, manufacturers have been required under Art. 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) to report actively exploited vulnerabilities and severe incidents affecting their products: an early warning notification within 24 hours, a notification within 72 hours, followed by a final report. Reports are submitted via ENISA's single reporting platform to the competent CSIRT, which in Germany is the BSI (Federal Office for Information Security). The obligation expressly also applies to products that were delivered years ago.
This article explains what must be reported, which content belongs in which stage and how to build a robust reporting process. An overview of all CRA obligations can be found on the page Cyber Resilience Act consulting.
What must be reported?
The CRA has two triggers for reporting:
| Trigger | What is meant | Example |
|---|---|---|
| Actively exploited vulnerability | a vulnerability in the product for which there is reliable evidence that a malicious actor has exploited it without permission of the system owner | A customer reports that a flaw in your router's firmware was used to break into their network. |
| Severe incident | an incident that negatively affects or is capable of negatively affecting the ability of the product to protect the availability, authenticity, integrity or confidentiality of important data or functions, or that has led or is capable of leading to the introduction of malicious code | Your update server is compromised and distributes manipulated updates to customers. |
The deadline starts when you become aware, not only once you have full proof. If you wait until all the details have been clarified, you will usually be too late.
Not subject to mandatory reporting, but eligible for voluntary reporting, are for example vulnerabilities that are not (yet) being exploited, or near misses. For these, your regular vulnerability handling under Annex I Part II applies, see CRA obligations for manufacturers.
Deadlines and content of the reporting stages
- 24 hours Early warning notification after becoming aware
- 72 hours Notification
- 14 days Final report for vulnerabilities, after a corrective or mitigating measure is available
| Stage | Actively exploited vulnerability | Severe incident |
|---|---|---|
| Early warning notification | within 24 hours of becoming aware; including the Member States in which the product has been made available | within 24 hours of becoming aware; including whether the incident is suspected of being caused by unlawful or malicious acts |
| Notification | within 72 hours; general information about the product, the nature of the exploit and of the vulnerability, corrective or mitigating measures taken, measures users can take | within 72 hours; nature of the incident, initial assessment, corrective or mitigating measures taken, measures users can take |
| Final report | no later than 14 days after a corrective or mitigating measure is available; description, severity, impact, information on the security update | within one month after the notification; detailed description, root cause, mitigation measures |
Note the difference in the final report: for vulnerabilities, the deadline runs from the availability of the remedy; for incidents, from the 72-hour notification.
Where are reports sent?
Reports are submitted via the single reporting platform operated by ENISA and go simultaneously to ENISA and to the CSIRT designated as coordinator. The competent CSIRT is that of the Member State in which the manufacturer has its main establishment in the EU. For manufacturers outside the EU, competence is determined by the authorised representative.
In Germany, the BSI has been coordinating CRA reports since 11 September 2026. Under the CRA-Durchführungsgesetz (German CRA implementation act), which the Bundestag passed on 15 October 2026, the BSI will additionally become the market surveillance authority. According to the Federal Ministry of the Interior, the act had not yet been promulgated at the time of going to press.
The receiving CSIRT forwards reports to the CSIRTs of the Member States in which the product has been made available and informs the market surveillance authorities where necessary.
Existing products: the frequently overlooked point
Most CRA obligations only apply to products that are placed on the market from 11 December 2027 or are substantially modified after that date. For the reporting obligation, the CRA makes an express exception (Art. 69(3)): it applies to all products within scope, including those that have been on the market for years.
Your reporting process must therefore cover the entire portfolio that has been delivered. This requires you to know which product versions are in use where, which components they contain and who is responsible for them internally, including for products whose development was completed long ago.
Informing users
In addition to reporting to the authorities, the manufacturer must inform the impacted users about the vulnerability or incident and, where necessary, about risk mitigation measures, where appropriate in a structured, machine-readable format. Plan communication channels and templates for this: customer portal, security advisories on the website, direct notification of business customers.
CRA, NIS2 and GDPR: three reporting obligations compared
A single incident can trigger several reporting obligations. A manufacturer that is itself covered by NIS2 and whose compromised update server also exposes customer data may have to report three times:
| CRA (Art. 14) | NIS2 (Section 32 BSIG) | GDPR (Art. 33) | |
|---|---|---|---|
| Trigger | actively exploited vulnerability or severe incident in the product | significant security incident in the operations of the entity | personal data breach |
| Who | manufacturers of products with digital elements | particularly important and important entities | controllers |
| Recipient | ENISA and CSIRT via the single reporting platform | joint reporting office of the BSI and the BBK (Federal Office of Civil Protection and Disaster Assistance) | competent data protection supervisory authority |
| First deadline | 24 hours | 24 hours | 72 hours |
Therefore build one incident process that checks at the outset which reporting obligations apply, instead of three separate procedures. Details on NIS2 reporting can be found in the article NIS2 reporting obligations.
How to build the reporting process
- Define responsibilities Named persons responsible for assessment and reporting, with deputies.
- Ensure availability A 24-hour deadline also runs at weekends. Arrange on-call duty or escalation routes.
- Bundle incoming channels Contact address for vulnerability reports, information from customers, suppliers, security researchers and authorities, your own monitoring.
- Define assessment criteria When is a vulnerability considered actively exploited, when is an incident severe? Record examples.
- Maintain a product inventory Versions, components (SBOM) and distribution for each product, including existing products.
- Prepare templates Content for the early warning notification, notification, final report and user information.
- Clarify access to the reporting platform Who reports, with which account?
- Rehearse Run through the procedure at least once using a realistic scenario and document the result.
- Link with other reporting obligations NIS2, GDPR and, where applicable, contractual reporting obligations towards customers.
For microenterprises and small enterprises, under Art. 64(10) no fines are imposed if they miss the 24-hour deadline for the early warning notification. The reporting obligation itself, however, also applies to them.
How SDG supports you
We advise you on the CRA reporting obligation and support you in building the process:
- Review of the current state: responsibilities, availability, incoming channels and product inventory
- Building the reporting process with assessment criteria, roles and templates for all reporting stages and for user information
- Linking with NIS2 and the GDPR, so that one incident process covers all reporting obligations; on request together with our work as external data protection officer
- Rehearsing the procedure using a realistic scenario
- Embedding in an ISMS based on ISO 27001, so that incident management works in the long term
Further CRA services can be found on the page Cyber Resilience Act consulting.
Frequently asked questions about the CRA reporting obligation
Since when has the reporting obligation under the Cyber Resilience Act applied?
Since 11 September 2026. The other obligations of the CRA only apply from 11 December 2027, so the reporting obligation must already be met today.
Does the CRA reporting obligation also apply to older products?
Yes. Under Art. 69(3), the reporting obligation applies to all products within scope, including those placed on the market before 11 December 2027. The reporting process must therefore cover the entire portfolio that has been delivered.
What is an actively exploited vulnerability?
A vulnerability for which there is reliable evidence that a malicious actor has actually exploited it without permission. A known vulnerability that has not been exploited does not have to be reported, but must be remediated as part of vulnerability handling.
Where do I report under the CRA?
Via ENISA's single reporting platform to ENISA and to the coordinating CSIRT of the Member State of your main establishment. In Germany, that is the BSI.
What deadlines apply to CRA reports?
Early warning notification within 24 hours, notification within 72 hours. For vulnerabilities, the final report is due no later than 14 days after a remedy is available; for severe incidents, within one month after the notification.
Do I have to inform my customers?
Yes. The manufacturer must inform impacted users about the vulnerability or incident and, where necessary, about risk mitigation measures.
What is the difference between the CRA and the NIS2 reporting obligation?
The CRA reporting obligation concerns vulnerabilities and incidents in the product and is addressed to manufacturers. The NIS2 reporting obligation concerns significant security incidents in the operations of a regulated entity. A company may be subject to both and then may have to report twice.
Legal sources: Regulation (EU) 2024/2847 (Cyber Resilience Act), in particular Art. 14, 16 and 69, ENISA, BSI: CRA implementation act, Section 32 BSIG
Note: This article provides general information and does not replace legal advice in individual cases.