What Art. 14 CRA requires
Art. 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) obliges manufacturers to report two types of event: actively exploited vulnerabilities in their products with digital elements, and severe incidents that have an impact on the security of those products. The obligation has applied since 11 September 2026 and also covers products placed on the market before that date (Art. 69(2)). It falls on the manufacturer, not the operator. Anyone who distributes a product under their own name or substantially modifies it is deemed a manufacturer (Art. 21 and 22) and is therefore subject to the reporting obligation themselves.
Reporting takes place in three stages with fixed deadlines. All of them run from the moment the manufacturer becomes aware, not from the end of the internal investigation.
The calculator derives the specific deadlines for the early warning, the notification and the final report from the time you became aware. No data is transmitted.
What is reportable
This distinction decides whether your team reports three times a year or three times a week.
Actively exploited vulnerability
A vulnerability for which there is reliable evidence that an attacker has exploited it on a system without the permission of the system owner (definition in Art. 3). Not reportable: vulnerabilities that your own team finds; vulnerabilities that a researcher reports responsibly; known vulnerabilities in components for which there is no indication of exploitation in your product. These cases go through vulnerability handling under Annex I Part II, which is described on the page on CRA requirements. But as soon as a customer, a CERT or a threat intelligence service provides evidence of exploitation in the wild, the 24-hour deadline starts.
Severe incident
An incident that has an impact on the security of the product and meets at least one of two criteria under Art. 14(5): it negatively affects the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or it has led, or is capable of leading, to the introduction or execution of malicious code. Typical examples: a compromised update infrastructure or a stolen signing key.
No product link, no CRA notification. A ransomware incident in your accounting department is not a severe incident within the meaning of the CRA as long as it does not affect the security of your products. It may, however, trigger a NIS-2 notification if your company is an important or essential entity.
Deadlines and content of the notifications
Each stage has its own minimum content. The early warning may be incomplete; its purpose is to let the CSIRT warn other affected parties. The 72-hour notification must contain an assessment. The final report documents the root cause and the remedy.
| Stage | Deadline | Content for an actively exploited vulnerability (Art. 14(2)) | Content for a severe incident (Art. 14(4)) |
|---|---|---|---|
| Early warning | 24 h after becoming aware | Affected product, indication of active exploitation, optionally the Member States in which the product is made available. | Affected product, indication of whether the incident is suspected to be caused by unlawful or malicious acts, optionally the Member States affected. |
| Notification | 72 h after becoming aware | General information on the product, nature of the exploitation and the vulnerability, corrective or mitigating measures taken or planned, severity, indicators of compromise where available. | General information on the nature of the incident, initial assessment, mitigating measures taken or planned, assessment of severity and impact. |
| Final report | No later than 14 days after a corrective or mitigating measure is available | Description of the vulnerability including severity and impact, information on the malicious actor where known, details of the security update or other corrective measures. | No later than 1 month after the 72-hour notification: detailed description of the incident, severity, impact, type of threat or root cause, mitigating measures taken and ongoing. |
Treat every notification as a document that may later form part of a fine proceeding: factual, dated, versioned, without speculation.
Reporting route via the ENISA platform and the CSIRT
Art. 16 obliges ENISA to operate a central reporting platform, the single reporting platform. It has been in operation since 11 September 2026. The manufacturer reports once; the platform forwards the notification to the CSIRT of the Member State in which the manufacturer has its main establishment and, in parallel, to ENISA. The competent CSIRT shares the notification without delay with the CSIRTs of the Member States in which the product is made available. Only in exceptional cases may it delay the dissemination for cybersecurity reasons; the conditions for this are set out in a delegated act of December 2025.
- For German manufacturers, the competent CSIRT is located at the BSI. Report via the ENISA platform nevertheless, not by e-mail to the BSI.
- Manufacturers without an establishment in the EU report to the CSIRT of the Member State in which the authorised representative is based or, if there is none, in which the product was first made available.
- Set up your access to the platform now. Registering on the night of the incident costs hours you do not have.
- Document the time you became aware and the time of each notification, with timestamp and responsible person.
Informing users
Notifying the authorities is only half the obligation. Under Art. 14(8), the manufacturer must inform the affected users and, where appropriate, all users without undue delay about the severe incident or the actively exploited vulnerability, including the risk mitigation and corrective measures that users can take themselves. The CSIRT may additionally require the manufacturer to inform the public if the manufacturer does not do so itself.
In practice, this means you need a security advisory with product name, affected versions, severity, workaround and update instructions. The template, the distribution list and the publication location (for instance a security page, machine-readable in CSAF format) should be in place before the first incident.
Interaction with NIS-2 reporting
CRA and NIS-2 use the same cadence of 24 hours and 72 hours but mean different things. The CRA notification concerns the product and is addressed to the manufacturer. The NIS-2 notification under Section 32 of the German BSIG concerns a significant incident in the organisation and is addressed to operators registered as important or essential entities. A mechanical engineering company with more than 50 employees is usually both: a manufacturer under the CRA and an entity under NIS-2, because manufacturing is listed in Annex 2 of the BSIG.
| Aspect | CRA (Art. 14) | NIS-2 (Section 32 BSIG) |
|---|---|---|
| Who reports | Manufacturer of the product | Affected entity (operator) |
| What | Actively exploited vulnerability, severe incident with a product link | Significant incident in the organisation itself |
| Where | ENISA single reporting platform, competent CSIRT | BSI reporting office |
| Deadlines | 24 h, 72 h, 14 days or 1 month | 24 h, 72 h, final report no later than 1 month |
Build a joint initial assessment step that asks both questions: Is a product affected? Is the organisation affected? After that, the notifications diverge. Details on the operator side are on the page on NIS-2 reporting obligations, and the distinction between the two frameworks in the comparison of CRA and NIS-2.
The internal process in five steps
All channels through which indications can arrive converge in one security mailbox: support, sales, the CVD point of contact under Annex I Part II, CERT alerts, threat intelligence. Every item is logged with a timestamp.
A named person decides on the basis of a checklist: Is there reliable evidence of exploitation? Is a product affected? Are the criteria under Art. 14(5) met? The result is documented, even if it reads "not reportable".
If the event is reportable, the early warning goes out via the ENISA platform no later than 24 hours after becoming aware. The technical analysis starts in parallel.
Within 72 hours, the notification with assessment and remediation plan follows. At the same time, the security advisory goes out to users. Product management, engineering and communications work to a release process agreed in advance.
The security update is provided free of charge and separately from functionality updates. No later than 14 days afterwards, or one month after the notification, the final report goes out. A review records what needs to be improved in the process.
Common mistakes
- Defining awareness too late. Anyone who lets the deadline start only once engineering has confirmed the issue loses days. Awareness begins with reliable evidence.
- No platform registration. Access to the single reporting platform is set up during the emergency instead of in advance.
- Notification without a product link. Internal IT incidents are reported under the CRA although no product is affected; conversely, product incidents are treated as mere IT disruptions.
- Forgetting users. The notification to the authorities is done, but the advisory arrives weeks later or never.
- Supply chain not involved. An exploited vulnerability in a component affects your product. Without an SBOM and supplier contacts, you find out too late.
Next steps
Use the deadline calculator above to get a feel for the cadence, then check whether your company could complete the five steps within the deadlines today. All other CRA dates are listed in the CRA timeline. In our CRA consulting, we set up the reporting process with you, dovetail it with NIS-2 reporting and test it in an exercise before the first real case arrives.

