CRA reporting applies since 11 September 2026. Are your products ready?Book a CRA scoping call

Home / CRA

CRA reporting: what to report, and when

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting their products. The first deadline is 24 hours.

Two things must be reported

An actively exploited vulnerability is a vulnerability for which there is reliable evidence that it has been exploited in the product. A severe incident is an incident that affects the security of the product, for example by compromising its data or functions.

The obligation applies to every product with digital elements on the EU market, including products placed on the market before December 2027. It is the first part of the CRA that is already in force.

Who reports to whom

  • The manufacturer of the product reports
  • Reports go through the single reporting platform operated by ENISA
  • They reach the CSIRT designated as coordinator in the member state of your main establishment, and ENISA
  • Affected users must also be informed about the issue and how to reduce its impact

Deadlines for an actively exploited vulnerability

Within 24 hours

Early warning

After you become aware of it, including the member states where the product is made available, if known.

Within 72 hours

Notification

General information about the product, the exploit and the vulnerability, and the measures taken or recommended.

Within 14 days

Final report

At the latest 14 days after a corrective or mitigating measure is available: description, severity, impact and the security update.

Deadlines for a severe incident

Within 24 hours

Early warning

After you become aware of it, including whether it is suspected to be caused by unlawful or malicious acts.

Within 72 hours

Notification

General information about the nature of the incident, an initial assessment and the measures taken or recommended.

Within one month

Final report

At the latest one month after the notification: description, severity, impact, threat type and mitigation measures.

What you need in place

A 24 hour deadline only works if the decisions are prepared before the first case.

1

Monitoring

Sources that tell you when a component in your products is exploited, from advisories to your own support channels.

2

Clear triggers

Criteria for when a finding counts as actively exploited and must be reported.

3

Roles and stand-in

Named people who decide and report, with cover for weekends and holidays.

4

Platform access

Registration and accounts for the single reporting platform, tested before they are needed.

5

Templates

Prepared texts for the early warning, notification, final report and user information.

6

Link to vulnerability handling

Reporting connected to analysis, fixes and updates, as Annex I Part II requires.

More CRA guides

As of October 2026. These guides explain the regulation in plain language and are not legal advice.

Where we can help

We set up the reporting process with your team and connect it to monitoring and fixes. AITIGRITY Vulnerability management supports the reports.

Where does your product stand?

Tell us about your product and the rule you are facing. You talk to an engineer from the first call.