CRA Article 14 answers a practical question for manufacturers of products with digital elements: if you discover an issue is being actively exploited or a serious security incident occurs, who do you notify, how quickly, and what information must the report contain?
In this article, we examine the different reporting tracks available to manufacturers when notifying CSIRT‑ENISA, depending on the nature and severity of the incident or vulnerability. For more in‑depth information on the CRA, readers can consult our EU Cyber Resilience Act Guide or visit our CRA Hub, where they will find detailed insights into the regulation and learn more about the services we provide to support manufacturers in preparing for CRA compliance.
Article 14 establishes the manufacturers’ reporting obligations, with two parallel reporting tracks that apply when manufacturers become aware of specific security events.
Actively exploited vulnerabilities refer to situations where a malicious actor is already taking advantage of a flaw in the product to cause harm. This track applies when there is confirmed, ongoing exploitation affecting users or other persons, such as an authentication bypass enabling unauthorized access or privilege escalation leading to data theft in a user‑facing component. When manufacturers detect such active misuse, they must quickly assess the nature and impact of the exploitation and initiate immediate corrective or mitigating measures to protect users and limit further damage.
Severe incidents refer to cybersecurity events that affect, or could affect, the security of the product or the manufacturer’s development, production, or maintenance processes. These incidents may not involve active exploitation but are considered severe when they pose a significant cybersecurity risk for users or other persons. Examples include malicious code injected into updates, compromise of code‑signing keys or signing services, or breaches of the source‑code repository or build system that impact shipped artifacts.
An incident is classified as severe when it meets either of the following conditions:
For both tracks, manufacturers report via the Single Reporting Platform. The notification becomes simultaneously accessible to the national coordinator CSIRT and to ENISA.
Reporting obligations under Article 14 apply from 11 September 2026. Manufacturers must report actively exploited vulnerabilities and severe incidents for all products with digital elements that fall within the scope of the CRA, including products placed on the market before 11 December 2027 (see Article 69(3)).
After becoming aware of an actively exploited vulnerability or a severe incident, manufacturers must inform impacted users.
Where a product contains an actively exploited vulnerability originating from an integrated component, the product manufacturer must notify it. The component manufacturer must also notify it if the component has been placed on the market.
A delegated act supplements the CRA by defining terms and conditions under which the first (coordinator) CSIRT receiving a notification may delay sharing it with other Member States’ CSIRTs. See the official text here: Delegated act.
1) What must manufacturers report under CRA Article 14?
Actively exploited vulnerabilities and severe security incidents, submitted via the Single Reporting Platform.
2) How fast do manufacturers need to report?
The clock starts when the manufacturer becomes aware of the vulnerability or incident. Follow the specific timelines defined by the platform and guidance once available.
3) Do legacy products need to be reported?
Yes, if they fall within the CRA’s scope, including products placed on the market before 11 December 2027.
4) What if the vulnerability comes from a third‑party component?
Both the product manufacturer and the component manufacturer (if the component is placed on the market) have notification duties.
5) Do manufacturers need to notify users as well as authorities?
Yes. Impacted users must be informed after the manufacturer becomes aware of the issue.
Additional information reading
Applus+ uses first-party and third-party cookies for analytical purposes and to show you personalized advertising based on a profile drawn up based on your browsing habits (eg. visited websites). You can accept all cookies by pressing the "Accept" button or configure or reject their use. Consult our Cookies Policy for more information.
They allow the operation of the website, loading media content and its security. See the cookies we store in our Cookies Policy.
They allow us to know how you interact with the website, the number of visits in the different sections and to create statistics to improve our business practices. See the cookies we store in our Cookies Policy.
Based on your behavior on the website (where you click, how long you browse, etc.) we establish parameters and a profile for you to display ads that correspond to your interests. See the cookies we store in our Cookies Policy.