Express + expert help

View pricing →
Skip to main content
tutorialCRA7 min read

CRA ENISA reporting — early warnings, notifications and final-report triggers

CRA Article 14 reporting: what triggers it, what the 24-hour, 72-hour and final reports must contain, which CSIRT receives them and what users must be told.

By CenitiaUpdated

Fact-checked against the law as of Reviewed by Vladimír Vician on How we check

Since 11 September 2026, Article 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) has required manufacturers to report two kinds of events through ENISA's Single Reporting Platform: actively exploited vulnerabilities in their products, and severe incidents having an impact on the security of their products. This page explains what triggers a report, what each stage must contain, where the report goes and what users must be told. For setting up access and roles, see the CRA reporting checklist.

What triggers a report

Actively exploited vulnerability. Article 3(42) of the Cyber Resilience Act defines it as a vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the permission of the system owner. The duty covers vulnerabilities contained in the manufacturer's own product.

Severe incident. Under Article 14(5), an incident having an impact on the security of the product is severe where it negatively affects, or is capable of negatively affecting, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or where it has led, or is capable of leading, to the introduction or execution of malicious code in the product or in a user's network and information systems.

Becoming aware. All deadlines run from the moment the manufacturer becomes aware. The Commission guidance on the application of the Cyber Resilience Act (C/2026/6013, paragraph 213) treats the manufacturer as aware once an initial assessment gives it a reasonable degree of certainty that one of the two events has occurred, and expects that assessment to start immediately. The guidance is not legally binding.

Third-party components. A vulnerability in a component must be reported under Article 14 only if it is actively exploited in the manufacturer's product (guidance, paragraph 218). The duty to report it upstream to the component's manufacturer or maintainer under Article 13(6) of the Cyber Resilience Act is separate.

Events known before 11 September 2026. A manufacturer that already knew of the active exploitation before that date does not have to report it retroactively (guidance, paragraph 217).

What each report must contain

StageActively exploited vulnerability (Article 14(2))Severe incident (Article 14(4))
Early warning, within 24 hours of becoming awareNotice of the vulnerability and, where applicable, the Member States in which the manufacturer knows the product has been made availableNotice of the incident, at least whether it is suspected of being caused by unlawful or malicious acts and, where applicable, the Member States in which the product has been made available
Notification, within 72 hours of becoming awareGeneral information, as available, on the product concerned, the general nature of the exploit and of the vulnerability, corrective or mitigating measures taken and measures users can take; where applicable, how sensitive the manufacturer considers the informationGeneral information, where available, on the nature of the incident, an initial assessment, corrective or mitigating measures taken and measures users can take; where applicable, how sensitive the manufacturer considers the information
Final reportNo later than 14 days after a corrective or mitigating measure is available: description of the vulnerability with severity and impact; where available, information on the malicious actor; details of the security update or other corrective measureWithin one month after the 72-hour notification: detailed description of the incident with severity and impact; the type of threat or likely root cause; applied and ongoing mitigation measures

The 72-hour notification and the final report are not needed where the information has already been provided. The CSIRT that receives the notification can also ask for an intermediate report on relevant status updates (Article 14(6)).

At intake, record the time you became aware, the affected product and version, and which of the two event types applies. Keep a copy of every submitted stage and of any confirmation the platform returns.

Two reporting paths and their deadlines (CRA Article 14)

Under Article 14 of the Cyber Resilience Act, a manufacturer notifies actively exploited vulnerabilities and severe incidents affecting the security of the product through the Single Reporting Platform, simultaneously to the CSIRT designated as coordinator and to ENISA. Both paths start with an early warning within 24 hours and a notification within 72 hours of becoming aware. The final stages differ: for an actively exploited vulnerability, a final report within 14 days after a corrective or mitigating measure is available (Article 14(2)(c)); for a severe incident, a final report within one month after the 72-hour notification (Article 14(4)(c)). Article 14(5) sets out when an incident is severe; there is no fixed monthly progress report. Article 14(8) also requires the manufacturer to inform impacted users. These duties have applied since 11 September 2026, including for products placed on the market before 11 December 2027 (Article 69(3)), and the platform is operational.

Where the report goes (CRA Article 14(7) and Article 16)

Reports are submitted on ENISA's Single Reporting Platform, to the CSIRT designated as coordinator in one Member State, and are available to ENISA at the same time. One notification per event is enough, even for a group with several EU subsidiaries.

Article 14(7) of the Cyber Resilience Act decides which CSIRT:

  • Manufacturer with a main establishment in the Union: the Member State where decisions on the cybersecurity of its products are predominantly taken. If that cannot be determined, the Member State where it has the establishment with the highest number of employees in the Union.
  • Manufacturer without a main establishment in the Union: in this order, the Member State of the authorised representative acting for the highest number of its products; of the importer placing the highest number of its products on the market; of the distributor making the highest number available; or the Member State with the highest number of users.

ENISA's FAQ warns that a notification sent to the wrong CSIRT may be invalidated and have to be resubmitted, so settle the choice before an event occurs.

The receiving CSIRT passes the notification on, without delay, to the CSIRTs of the Member States where the manufacturer has said the product is available (Article 16(2)). In exceptional circumstances that dissemination can be delayed on justified cybersecurity grounds; Commission Delegated Regulation (EU) 2026/881 sets the conditions.

Informing users (CRA Article 14(8))

Reporting to the authorities is not the whole duty. Article 14(8) of the Cyber Resilience Act requires the manufacturer to inform the impacted users, and where appropriate all users, of the actively exploited vulnerability or severe incident and, where necessary, of the risk mitigation and corrective measures they can deploy, where appropriate in a structured, machine-readable format. If the manufacturer does not inform users in good time, the notified CSIRTs may do so.

The Commission guidance (C/2026/6013, paragraphs 220 and 221) reads this duty as risk-based and proportionate. Detailed information can be limited to the users or customers concerned, in particular where publishing technical details could itself increase the risk. Broader disclosure may be appropriate once the vulnerability has been addressed or mitigated.

Older products and products out of support

Article 69(3) of the Cyber Resilience Act applies Article 14 to all in-scope products placed on the market before 11 December 2027. According to the Commission guidance (paragraph 210), the reporting duty also continues after a product's support period has ended, unlike the vulnerability-handling requirements of Annex I Part II.

CRA penalty ceilings (Regulation (EU) 2024/2847, Article 64)

Under Article 64(2) of the Cyber Resilience Act, non-compliance with the essential cybersecurity requirements in Annex I and with the obligations in Articles 13 and 14 can be fined up to EUR 15 million or, for an undertaking, up to 2.5 % of total worldwide annual turnover, whichever is higher. Other infringements have lower ceilings. Article 64(10) spares microenterprises and small enterprises fines for missing the 24-hour early-warning deadline; it does not exempt them from reporting. These are maximum amounts for Member States’ penalty rules, not automatic fines, and they concern the Cyber Resilience Act only. The Annex I and Article 13 obligations apply from 11 December 2027; Article 14 has applied since 11 September 2026.

Primary references

FAQ

Frequently asked questions

  • When does the CRA 24-hour clock start?

    When the manufacturer becomes aware of the actively exploited vulnerability or severe incident (Article 14(2)(a) and 14(4)(a) of the Cyber Resilience Act). The Commission guidance (C/2026/6013, paragraph 213) says a manufacturer is aware once, after an initial assessment of a suspicious event or a report from a third party, it has a reasonable degree of certainty that a vulnerability in its product is being actively exploited or that a severe incident has compromised the security of its product. That assessment should start immediately.

  • Which CSIRT does a manufacturer outside the EU report to?

    Article 14(7) of the Cyber Resilience Act sets an order. Without a main establishment in the Union, the manufacturer uses the CSIRT designated as coordinator in the Member State of the authorised representative acting for the highest number of its products; failing that, of the importer placing the highest number on the market; failing that, of the distributor making the highest number available; failing that, the Member State with the highest number of users.

  • Do I have to report a vulnerability in a third-party component?

    Only if it is actively exploited in your product. The Commission guidance (C/2026/6013, paragraph 218) explains that a component vulnerability that cannot be exploited in your product, or has not been exploited in it, is not an actively exploited vulnerability contained in your product, so Article 14 does not require a report. You must still handle the vulnerability under Annex I Part II and report it to the component's manufacturer or maintainer under Article 13(6) of the Cyber Resilience Act.

  • Does the manufacturer have to tell users about an exploited vulnerability?

    Yes. Article 14(8) of the Cyber Resilience Act requires the manufacturer to inform the impacted users, and where appropriate all users, of the vulnerability or incident and, where necessary, of risk mitigation and corrective measures they can deploy. If the manufacturer does not do so in good time, the CSIRTs may inform users. The Commission guidance (C/2026/6013, paragraph 220) says this duty is applied in a risk-based and proportionate way and does not mean that details must be made public indiscriminately.

Continue reading

Related guides

Put this into practice

Free tools & references

New to the terminology? Browse the compliance glossary — plain-English, citation-backed definitions of every term above.