One obligation from the Cyber Resilience Act (Regulation (EU) 2024/2847) already applies today: if attackers demonstrably exploit a vulnerability in your product, or a severe incident hits your product, you report it with an early warning within 24 hours. These CRA reporting obligations have applied since 11 September 2026 (Art. 14 and Art. 71(2) CRA), also to products you sold earlier, as far as they fall under the CRA (Art. 69(3)).
If you decide in advance who reports and how, you can act calmly when it happens. This article shows what is reported, where, who in your company should handle it and what else is due by December 2027. What the CRA requires overall is in the overview Cyber Resilience Act: obligations for manufacturers.
What the CRA reporting obligations require
You have to report two kinds of events:
- An actively exploited vulnerability in your product: there is reliable evidence that someone has actually attacked the vulnerability without the permission of the system owner (Art. 14(1) and Art. 3(42)).
- A severe incident having an impact on the security of your product. It is severe if it negatively affects or is capable of negatively affecting the protection of sensitive or important data or functions, or if it has led or is capable of leading to malicious code in the product or in a customer’s network (Art. 14(3) and (5)).
A known vulnerability in a library with no evidence of an attack is not a reportable event by itself. You may report such vulnerabilities, cyber threats and near misses voluntarily (Art. 15).
Reporting deadlines: 24 hours, 72 hours, final report
The deadlines run from the moment you become aware. Under the draft Commission guidance of 27 July 2026 this is the case when, after an initial assessment, you have a reasonable degree of certainty (C(2026) 5252, para. 213). The guidance will only apply once formally adopted in all official languages, and even then it is not binding.
For an actively exploited vulnerability (Art. 14(2)):
- Early warning: without undue delay, at the latest 24 hours after becoming aware, naming the EU member states in which, to your knowledge, the product has been sold.
- Notification: without undue delay, at the latest 72 hours after becoming aware, with general information on the product, the nature of the exploit and the measures you have taken or your customers can take.
- Final report: at the latest 14 days after a corrective or mitigating measure is available, with a description, the severity and the update provided.
For a severe incident (Art. 14(4)):
- Early warning: without undue delay, at the latest 24 hours after becoming aware, stating whether you suspect an unlawful or malicious act.
- Notification: without undue delay, at the latest 72 hours after becoming aware, with an initial assessment and the measures taken.
- Final report: within one month of the notification.
You also inform the affected customers about the vulnerability or incident and about what they can do themselves (Art. 14(8)).
Where to report: the ENISA single reporting platform
You report online via the single reporting platform of ENISA, the EU agency for cybersecurity, at portal.cra-srp.enisa.europa.eu. There the report goes to the CSIRT of your country, the national body for cybersecurity incidents, and is visible to ENISA at the same time (Art. 14(7)).
The competent CSIRT is the one in the member state where you mainly take the decisions on the cybersecurity of your products; if that cannot be determined, the establishment with the most employees counts (Art. 14(7)). Which body that is in your country is shown in a list that ENISA links on its page about the reporting platform. The platform has been running since 11 September 2026, since 4 November 2026 as version 1.3. For questions, the CSIRTs offer a helpdesk, in particular for small and medium-sized enterprises (Art. 17(6)).
Manufacturers without a main establishment in the EU, for example from Switzerland, report to the CSIRT where their authorised representative in the EU is based, otherwise where the importer is based, then the distributor, and finally to the CSIRT of the member state with the most users (Art. 14(7)).
Who reports in your company: our recommendation
The CRA does not say who in your company reports. The following points are our recommendation; the regulation sets no deadline for this preparation.
Responsibility:
- One person with insight into the product and its technology handles the report, for example the head of development or service. This person can judge whether a vulnerability is actually being attacked.
- A second person stands in, so that the 24 hours can be met during holidays and at weekends.
- Management learns of every report immediately.
Preparation includes a list of your products with the countries you deliver to, because the early warning asks for them. Add short templates for the reports and a clear route by which hints of attacks reach you, for example from customers or from warnings by your suppliers. These points are also in the checklist below.
Do the reporting obligations apply to older products?
Yes, to all products that fall under the CRA, even if they were placed on the market before 11 December 2027 (Art. 69(3)). The other obligations only apply to such legacy products if you substantially modify them afterwards (Art. 69(2)). Under the draft Commission guidance, the reporting obligation continues after the end of the support period (para. 210).
For microenterprises and small enterprises, Art. 64(10) provides that no fine is imposed if they miss the 24-hour early warning. How far this exemption reaches is not clear from the wording. The notification and the final report remain mandatory in any case.
CRA deadlines at a glance
These dates are in the text of the regulation; as of 16 November 2026, no legal act has changed them:
- 10 December 2024: the CRA enters into force (Art. 71(1)).
- 11 June 2026: the rules on designating testing bodies apply (Chapter IV, Art. 71(2)).
- 11 September 2026: the reporting obligations apply, also to products already on the market (Art. 71(2) and Art. 69(3)). The ENISA reporting platform has been running since that day.
- 11 December 2026: by this date, enough notified bodies should be available (Art. 35(2)).
- 11 December 2027: for products placed on the market from then on, all other obligations apply, including the SBOM, vulnerability handling, technical documentation, conformity assessment and CE marking (Art. 71(2)). From this day, open-source software stewards also report (Art. 24(3)).
For radio equipment, cybersecurity requirements under the Radio Equipment Directive have applied since 1 August 2025, from Delegated Regulation (EU) 2022/30 with the EN 18031 series of standards. The Commission has repealed this Delegated Regulation with effect from 11 December 2027 (Delegated Regulation (EU) 2026/339, Art. 1).
Cyber Resilience Act 2027: what changes on the cut-off date
From 11 December 2027, products you newly place on the market need technical documentation, a conformity assessment, an EU declaration of conformity and a CE marking before they are sold (Art. 13(12)). For devices and machines, every single unit counts under the draft Commission guidance, even for a type sold for years (paras. 11 and 33 to 38). For software, all copies of an unchanged version count as placed on the market with the first offer (paras. 13 and 14).
The standards with which you can demonstrate the requirements are still being drafted. On 10 November 2026 the Commission extended the deadlines for all product-specific and some general standards by three months. Standards are voluntary, but for class I products they decide whether you may assess the product yourself (Art. 32(2)).
What may still change
The Commission proposal for a Digital Omnibus (COM(2025) 837) does not amend the CRA. It would establish in the NIS2 Directive that a CRA report on a severe incident also counts as a NIS2 report, insofar as it contains the information required there (Art. 23(4) NIS2). The proposal has not been adopted yet. It is also open whether the Commission will still lay down the format and procedure of the reports (Art. 14(10)).
CRA checklist: step by step to 2027
The list is ordered by urgency. A date only appears where the regulation sets a deadline; everything else is our recommendation.
Now, for the reporting obligations (recommendation, no separate deadline):
- ☐ List the products that fall under the CRA and that you offer or have offered in the EU, with the countries you deliver to (Art. 69(3)).
- ☐ Determine the competent CSIRT, name the reporting person and a deputy (Art. 14(7)).
- ☐ Clarify who decides whether a vulnerability is actively exploited.
- ☐ Prepare templates for the early warning, notification, final report and customer information (Art. 14(2), (4) and (8)).
By 11 December 2027, for products placed on the market from then on:
- ☐ Classify each product: default, class I, class II or critical (Art. 7, Annexes III and IV). Do this early, because it decides whether you need a notified body.
- ☐ Document the risk assessment for each product (Art. 13(2) to (4)).
- ☐ Generate an SBOM for each product in the build, at least with the top-level dependencies (Annex I, Part II, point 1).
- ☐ Define how you handle vulnerabilities: contact address, rules for coordinated disclosure, free security updates, separate from feature updates where possible (Annex I, Part II).
- ☐ Set the support period, at least five years, and state the end date at the time of purchase (Art. 13(8) and (19)).
- ☐ Draw up the technical documentation and user information (Art. 31, Annexes II and VII).
- ☐ Carry out the conformity assessment, issue the EU declaration of conformity, affix the CE marking (Art. 28, 30 and 32).
Ongoing from 11 December 2027:
- ☐ Test regularly and fix vulnerabilities without delay (Annex I, Part II, points 2 and 3). The CRA does not say how often to check the SBOM against vulnerability databases; our recommendation is a fixed rhythm, for example with every release and once a month.
- ☐ Keep every security update available for at least ten years or until the end of the support period, whichever is longer (Art. 13(9)).
- ☐ Keep the technical documentation and the declaration of conformity for at least ten years, longer if the support period is longer (Art. 13(13)).
- ☐ Apply the CRA in full whenever you substantially modify a legacy product (Art. 69(2)).
What an SBOM is and what to arrange for it is covered in How to create an SBOM with CycloneDX and SPDX.
Note: this article summarises the deadlines and reporting obligations under the regulation and the draft Commission guidance as of 16 November 2026. It is not legal advice. Whether an event must be reported is for you as the manufacturer to decide, as is your EU declaration of conformity.
SBOM and vulnerability monitoring as a service
For the reporting obligations, what counts is knowing quickly which building blocks are in your product. We create the SBOM of your product, check it every month and send you a report with an update recommendation. It also states whether attacks on a vulnerability have been publicly reported. We chose the monthly rhythm; the CRA does not prescribe one. Whether a vulnerability in your product is actively exploited and therefore reportable is still for you to decide and report.
The service is in preparation. Those who sign up hear first when it launches and what it costs: waiting list for the SBOM and vulnerability service.