shipcra

CRA Article 14: reporting actively exploited vulnerabilities and severe incidents

Reviewed 3 min read

Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents affecting their products. The sequence is an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days of a fix for a vulnerability, or within one month for an incident. Reports go through the EU single reporting platform.

Key facts

Applies from
11 September 2026, including products already on the market
Early warning
Within 24 hours of becoming aware
Notification
Within 72 hours of becoming aware
Final report, vulnerability
No later than 14 days after a fix or mitigation is available
Final report, severe incident
Within one month of the notification
Where
The single reporting platform, to the coordinating CSIRT and ENISA

What triggers a report

An actively exploited vulnerability. A vulnerability in your product for which there is reliable evidence that a malicious actor has exploited it in a system without the owner’s permission. A proof of concept on a blog isn’t enough on its own; an attack seen in the wild is.

A severe incident having an impact on the security of your product. An incident that affects, or can affect, 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 into the product or the systems of its users. A compromised build server that pushed a tampered update is the textbook case.

The clock starts when you become aware, not when the attack began.

The three deadlines

Step Actively exploited vulnerability Severe incident
Early warning Within 24 hours, including the Member States where the product is available Within 24 hours, including whether it may be caused by unlawful or malicious acts
Notification Within 72 hours: the product, the nature of the exploit, measures taken and measures users can take Within 72 hours: the nature of the incident, an initial assessment and the measures
Final report No later than 14 days after a fix or mitigation is available: description, severity, impact, root cause and the update Within one month of the notification: description, severity, impact, root cause and mitigation

You can send an early warning with incomplete information. Its job is to raise the flag on time.

Where reports go

Reports are submitted through the single reporting platform run by ENISA. They go to the computer security incident response team (CSIRT) designated as coordinator in the Member State where you have your main establishment, and simultaneously to ENISA. Manufacturers established outside the EU follow specific rules in the regulation to determine the Member State.

You also inform the users affected, and where appropriate all users, in a structured, machine-readable format where appropriate, so they can protect themselves.

Small companies and stewards

Micro and small enterprises can’t be fined for missing the 24-hour early-warning deadline, but the duty to report stays. Open-source software stewards have a lighter regime and aren’t subject to administrative fines; see the Cyber Resilience Act and open source.

Get ready before you need it

Twenty-four hours is short when you discover the problem on a Saturday. Prepare these now:

  1. Know what you shipped. An up-to-date SBOM per release tells you within minutes which versions contain the affected component.
  2. Watch the right sources. Match your components daily against vulnerability databases such as OSV, and watch the known-exploited lists published by security agencies.
  3. Open an intake channel. A published vulnerability disclosure policy and a security.txt file make sure researchers reach you rather than the press.
  4. Draft the reports in advance. Prepare templates for the three steps with the fields above, so the first one takes minutes.
  5. Decide who reports. Name the person who submits reports and a backup, and make sure both can access the platform.
  6. Rehearse once. A one-hour tabletop exercise on a made-up exploited dependency shows where the process breaks.

Reporting is not the same as disclosure

Article 14 is a duty to authorities for exploited vulnerabilities and severe incidents. Your coordinated vulnerability disclosure policy is how anyone can report any vulnerability to you. They meet when a report you receive turns out to describe something already exploited: then both apply.

Questions

Do I have to report every vulnerability?

No. Article 14 covers vulnerabilities that are actively exploited, meaning there is reliable evidence a malicious actor has exploited them, and severe incidents. Ordinary bugs and vulnerabilities found by researchers go through your disclosure process instead.

Does Article 14 apply before December 2027?

Yes. It has applied since 11 September 2026, and it also covers products placed on the market before 11 December 2027.

Can a small company be fined for missing the 24-hour deadline?

Micro and small enterprises can’t be fined for missing the 24-hour early-warning deadline. They still have to report, and the other deadlines and obligations still apply.

Do I have to tell users?

Yes. After becoming aware, you inform the users affected, and where appropriate all users, about the vulnerability or incident and the measures they can take.

Sources

  1. Regulation (EU) 2024/2847, Articles 14, 64 and 69, EUR-Lex
  2. Cyber Resilience Act: reporting obligations, European Commission

This guide explains the regulation in general terms. It isn’t legal advice for your product.

Keep the reporting clock in view.

Watch checks your components against OSV.dev every day and prepares Article 14 drafts when something is actively exploited.

Join early access