Severe incident
A severe incident, in the regulation’s sense, is an incident that seriously affects a product’s security, for example because attackers introduced malicious code. The manufacturer must report it just like an actively exploited vulnerability, with the same 24- and 72-hour deadlines but a different final report deadline.
Severe incident: definition
The criteria are in Article 14(5) of Regulation (EU) 2024/2847. An incident affecting the product’s security is severe if it negatively affects, or is capable of affecting, the product’s ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has led or could lead to the introduction or execution of malicious code in the product or in a user’s systems.
The term incident itself refers to the NIS2 Directive (Article 3(43)). Reports go through the Single Reporting Platform to the competent CSIRT and to ENISA.

Severe incident in practice
It does not have to happen at the customer’s site. If attackers compromise a manufacturer’s build environment or take over its update server, the security of every shipped device can be affected. Supply chain attacks like these are exactly what the regulation wants to capture.
The manufacturer also informs affected users about it and about measures they can take themselves (Article 14(8)).
Attackers gain access to a manufacturer’s signing key and distribute tampered firmware through the official update channel. That is a severe incident, because malicious code reaches customer devices. The manufacturer submits an early warning within 24 hours, the incident notification within 72 hours and the final report no later than one month after that.
What to do
- Include build, signing and update infrastructure in incident detection
- Add the Article 14(5) criteria to the incident response handbook
- Align how these reports interact with any NIS2 reports
- Prepare templates for informing users
Common misconceptions
“Only data breaches are reportable.”
An attack on functions, such as remote control of a device, can be severe without any data leaving.
“Damage must already have occurred.”
It is enough that the incident could harm the protective capability or lead to malicious code being executed.
Related terms
Actively exploited vulnerability
The other trigger for Article 14 reporting.
Read the entryFor incidents, the final report is due one month after the notification.
Read the entrySingle Reporting Platform (SRP)
The platform the manufacturer uses to report it.
Read the entryWhere does your product stand on the Cyber Resilience Act?
The free Product Check shows within minutes which of your products are in scope. The Readiness Check shows how well your company is prepared for the obligations.
Free, no login, no email. See who is in scope or go straight to the compliance software.