The reporting clock is already running. Here is who must report, what the deadlines are, and the intake, triage and disclosure process a product team needs behind them.
In short
CRA reporting means that manufacturers of products with digital elements must report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform: an early warning within 24 hours, a notification within 72 hours and a final report later. These duties have applied since 11 September 2026, for products already on the market too.
The Cyber Resilience Act (Regulation (EU) 2024/2847) arrives in two waves. Most of it, including CE marking and the essential requirements, applies from 11 December 2027. CRA reporting came first. This guide is written by Devies, a Gothenburg-based product and engineering consultancy, for CTOs, product owners and engineering leads who build software, connected devices or apps sold in the EU. It explains what the reporting duty covers, how it connects to the vulnerability handling requirements, and what to set up so that a 24-hour deadline is realistic rather than theoretical.
Who is covered by CRA reporting, and what must be reported?
CRA reporting applies to every manufacturer that places a product with digital elements on the EU market, and it covers two kinds of events: actively exploited vulnerabilities and severe incidents affecting the security of the product.
Some definitions help:
- A product with digital elements is software or hardware, including its remote data processing, that connects directly or indirectly to a device or network. Apps, firmware, desktop software and connected devices are all in scope; pure SaaS generally is not, unless it is the remote processing of a product.
- An actively exploited vulnerability is one for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. A theoretical weakness found in a pentest is not enough.
- A severe incident is one that harms, or can harm, the product's ability to protect the availability, authenticity, integrity or confidentiality of data or functions, or that has led or can lead to malicious code being introduced or executed in the product or the user's systems.
As of October 2026, the European Commission's CRA reporting page states that manufacturers have been required to report since 11 September 2026, and that this includes products placed on the market before the main CRA requirements apply. Open-source software stewards follow later, from 11 December 2027. Importers and distributors do not report to the authorities themselves, but must inform the manufacturer when they learn of a vulnerability.
What are the deadlines and where do reports go?
Reports go through ENISA's Single Reporting Platform to the national CSIRT designated as coordinator in the country of your main establishment, with ENISA receiving them at the same time, and the clock starts when you become aware.
Step
Actively exploited vulnerability
Severe incident
Early warning
Actively exploited vulnerability
Within 24 hours of becoming aware
Severe incident
Within 24 hours of becoming aware
Notification
Actively exploited vulnerability
Within 72 hours, with general information, corrective measures and how sensitive the information is
Severe incident
Within 72 hours, with the nature of the incident, initial assessment and mitigations
Final report
Actively exploited vulnerability
No later than 14 days after a corrective or mitigating measure is available
Severe incident
Within one month of the 72-hour notification
Inform users
Actively exploited vulnerability
After becoming aware, with mitigation measures
Severe incident
After becoming aware, with mitigation measures
The legal text is Article 14 of the Cyber Resilience Act on EUR-Lex. The ENISA Single Reporting Platform has been operational since 11 September 2026, and one submission reaches both the coordinating CSIRT and ENISA, so you do not file separately in every country where the product is sold.
If the same event also hits your own organisation, other clocks may run in parallel: NIS2 incident reports for covered entities and GDPR breach notifications. Our incident response plan guide shows how to put all of them in one reporting matrix.
What does CRA vulnerability handling require behind the report?
Vulnerability handling (in Swedish, CRA sårbarhetshantering) is the continuous process Annex I Part II of the CRA requires for the whole support period, and reporting is only the visible tip of it.
Annex I Part II lists eight duties. Paraphrased, the manufacturer must:
- Identify and document vulnerabilities and components, including a software bill of materials covering at least the top-level dependencies.
- Address and remediate vulnerabilities without delay, including with security updates, kept separate from feature updates where technically feasible.
- Test and review the security of the product regularly.
- Once a fix is available, publicly disclose information about fixed vulnerabilities: a description, affected products, impact, severity and how users can remediate.
- Put in place and enforce a coordinated vulnerability disclosure policy.
- Make it easy to report vulnerabilities, including by providing a contact address.
- Provide mechanisms to distribute updates securely, automatically where appropriate.
- Distribute security updates without delay and, as a rule, free of charge, with advisory messages.
Article 13 adds that the support period should normally be at least five years, unless the product is expected to be in use for less, and that a vulnerability found in an integrated component must be reported to whoever maintains it. In practice, the SBOM is what turns "a new vulnerability was published" into "these three firmware versions are affected" in minutes rather than days. For format choices and automation, see what an SBOM is and why the CRA requires one.
What should product teams set up first?
The fastest route to compliance is to build one intake-to-disclosure pipeline that serves both the vulnerability handling duties and the 24-hour report, rather than two separate processes.
Use this as a first-steps checklist:
- Name an owner and a deputy for product security reporting, with authority to submit an early warning without waiting for a board meeting.
- Register on the Single Reporting Platform and check which CSIRT is the coordinator for your main establishment.
- Publish a disclosure policy and a security contact, for example a security.txt file and a monitored mailbox, so researchers and customers know where to report.
- Generate an SBOM in every build and feed it into a tool that matches components against vulnerability databases and the CISA Known Exploited Vulnerabilities catalogue.
- Define triage criteria: what counts as "actively exploited", who decides, and how the decision and its timestamp are recorded. The awareness moment starts the clock, so log it.
- Prepare report templates for the early warning, the notification and the final report, with the fields the platform asks for.
- Prepare user communication: advisory templates, a page for security advisories and a channel to reach customers of each product.
- Check your update path: can you ship a signed security fix to every supported version without bundling unrelated features?
- Rehearse once: run a tabletop exercise with a fictional exploited vulnerability and time the steps from intake to early warning.
Devies saw the value of this kind of integration in its work with Zenseact on safety-critical automotive software, where an SBOM-based vulnerability and dependency tracking solution was hosted and integrated into CI/CD, alongside incident response processes, rather than run as a separate compliance track.
What are the common mistakes?
The most common mistake is treating CRA reporting as a legal task, when the bottleneck is almost always technical: knowing quickly which shipped versions contain the affected component.
Watch for these patterns:
- No inventory of shipped versions. Without a record of which build runs at which customer, impact assessment takes days.
- Waiting for certainty. The early warning is meant to be early. You can update it in the 72-hour notification.
- Confusing severity with exploitation. A critical CVSS score does not trigger reporting on its own; evidence of active exploitation does. A medium-severity bug that is being exploited does trigger it.
- Forgetting legacy products. Reporting covers products already on the market, including older models still in use.
- Mixing security fixes with features. Customers delay large updates. Separate security releases reach users faster and satisfy the Annex I expectation.
For the wider picture of essential requirements, conformity assessment and the 2027 deadline, read how to prepare your product for the Cyber Resilience Act.
Devies
Want a second opinion?
Devies, a Gothenburg-based product and engineering consultancy, works on questions like this with Nordic product and IT teams. Tell us where you are and we will suggest a sensible first step.
Frequently asked questions
When did CRA reporting obligations start?
Manufacturers have been required to report actively exploited vulnerabilities and severe incidents since 11 September 2026, the date ENISA's Single Reporting Platform became operational. The obligation applies to products with digital elements already on the EU market, not only new ones. The rest of the Cyber Resilience Act, including essential requirements and CE marking, applies from 11 December 2027. Open-source software stewards have reporting duties from that later date.
Do we have to report every vulnerability we find?
No. Mandatory reporting covers actively exploited vulnerabilities, meaning there is reliable evidence that someone has exploited the flaw without permission, and severe incidents affecting the product's security. Vulnerabilities found in your own testing or reported by researchers must still be handled and fixed under Annex I, and disclosed once fixed, but they are not reported to the CSIRT unless exploitation is confirmed. Voluntary reporting is also possible.
What is the 24-hour early warning supposed to contain?
The early warning is short. For an actively exploited vulnerability it states the issue and, where applicable, the EU member states where the product is available. For a severe incident it also indicates whether the incident is suspected to be caused by unlawful or malicious acts. Detailed information about corrective measures and impact comes in the 72-hour notification, and the full analysis in the final report.
Does the CRA require an SBOM to be published?
No. The Cyber Resilience Act requires manufacturers to draw up an SBOM in a commonly used, machine-readable format covering at least the top-level dependencies, and to include it in the technical documentation. Market surveillance authorities can request it. Sharing it with customers is optional. Its practical value is internal: it is how you find out quickly which products and versions a new vulnerability affects.










