Compliance GuideEffective 11 Sept 2026

What does CRA Article 14 require manufacturers to report, and by when?

CRA Article 14 requires a manufacturer to report each actively exploited vulnerability and severe incident in its product to the coordinator CSIRT and ENISA, with an early warning within 24 hours, a notification within 72 hours and a final report.

Article 14 of Regulation (EU) 2024/2847 introduces a three-stage reporting cascade for actively exploited vulnerabilities and severe incidents. From 11 September 2026, every manufacturer of a product with digital elements on the EU market, wherever it is based, has to be ready to file the 24-hour early warning. This page covers the trigger criteria, the three deadlines, and how to operate the workflow.

Key Takeaways
  • • Article 14 reporting applies from 11 September 2026 to every manufacturer of a product with digital elements on the EU market.
  • • An actively exploited vulnerability and a severe incident each start a 24-hour early warning and a 72-hour notification, both counted from awareness.
  • • The final report for an actively exploited vulnerability is due 14 days after a corrective or mitigating measure is available.
  • • The final report for a severe incident is due one month after the 72-hour incident notification.
  • • Every report goes through the ENISA Single Reporting Platform to the coordinator CSIRT and ENISA at the same time.

Is there a platform that handles CRA Article 14 reporting?

Two platforms handle CRA Article 14 reporting, with different jobs. The ENISA Single Reporting Platform receives each Article 14 notification, which a person at the manufacturer files there. CVD Portal is a preparation platform that builds the early warning, the 72-hour notification and the final report, tracks each deadline and keeps the evidence. No vendor platform files the report, because ENISA offers manufacturers no submission API.

ENISA Single Reporting PlatformPreparation platform, for example CVD Portal
Operated byENISA, under Article 16(1)A software vendor
JobReceives each notification and makes it available to the coordinator CSIRT and ENISA at the same timeBuilds the content of each stage from the vulnerability record and shows a timer for each deadline
Who actsA person at the manufacturer, signed in with an EU Login accountThe team of the manufacturer, before the filing
Required by the CRAYes, by Article 14(7)No. A manufacturer can prepare each report by hand

Read how the ENISA Single Reporting Platform works and which CVD Portal plan has the Article 14 packages.

The three-stage reporting cascade

All three stages submit to ENISA and the relevant national CSIRT via the Single Reporting Platform. The clock starts when the manufacturer becomes aware of the triggering event. Article 14 sits inside a wider obligation set, and the EU Cyber Resilience Act explained article by article covers all of it.

Flow diagram of the CRA Article 14 reporting chain. A security researcher sends an encrypted vulnerability report into the CVD Portal platform. Inside the platform, intake and encryption feeds triage and threat intelligence, which feeds SLA tracking. Two timed arrows leave the platform for ENISA and the national CSIRT, one carrying the 24 hour early warning and one carrying the 72 hour notification. The chain ends in an SRP-ready compliance package.
A vulnerability report reaches the coordinating CSIRT through one system. The platform runs intake, enrichment and the deadline clocks. The active exploitation judgement and the filing itself stay with the manufacturer.
  1. 24 hours

    Early warning

    Notify ENISA and the relevant national CSIRT via the Single Reporting Platform that an actively exploited vulnerability or a severe incident has been identified. The early warning is brief. It names the Member States where you know the product was made available and, for a severe incident, whether you suspect unlawful or malicious acts.

  2. 72 hours

    Notification

    Submit a notification with general information about the product, the general nature of the exploit and the vulnerability, or the nature of the incident with an initial assessment. Add the corrective or mitigating measures taken, the measures users can take and, where applicable, how sensitive the information is.

  3. 14 days / 1 month

    Final report

    For an actively exploited vulnerability, submit the final report within 14 days after a corrective or mitigating measure is available. It describes the vulnerability with its severity and impact, any known malicious actor exploiting it, and the security update shipped. For a severe incident, submit the final report within one month after the 72-hour incident notification. It describes the incident with its severity and impact, the likely threat type or root cause, and applied plus ongoing mitigations.

Two trigger conditions

Article 14 applies to two distinct categories. The reporting process is the same; the qualifying event differs.

Actively exploited vulnerability

A vulnerability in a product with digital elements that the manufacturer has reasonable evidence is being exploited in the wild. Evidence can come from incident response, threat intelligence, third-party reports, or internal telemetry.

Severe incident

An incident having an impact on the security of the product with digital elements. Article 14(5) makes it severe when it affects, or can affect, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or when it has led, or can lead, to malicious code running in the product or in a user's systems.

What goes in each report

24h early warning

Identification of the manufacturer and the affected product, indication of the issue (vulnerability or incident), the suspected unlawful or malicious nature where relevant, and any known cross-border impact. The early warning is deliberately short.

72h notification

General information about the product, the general nature of the exploit and the vulnerability, or the nature of the incident with an initial assessment. The corrective or mitigating measures taken, the corrective or mitigating measures that users can take and, where applicable, how sensitive the manufacturer considers the information to be (Article 14(2)(b) and 14(4)(b)).

Final report

For an actively exploited vulnerability, the final report is due within 14 days after a corrective or mitigating measure is available (Article 14(2)(c)). It describes the vulnerability with its severity and impact, any known malicious actor exploiting it, and the security update or other corrective measure made available. For a severe incident, the final report is due within one month after the 72-hour incident notification (Article 14(4)(c)). It describes the incident with its severity and impact, the likely threat type or root cause, and applied plus ongoing mitigation measures.

Frequently asked

Is there a platform that handles CRA Article 14 reporting?
Two platforms handle CRA Article 14 reporting, with different jobs. The ENISA Single Reporting Platform receives each Article 14 notification, which a person at the manufacturer files there. CVD Portal is a preparation platform that builds the early warning, the 72-hour notification and the final report, tracks each deadline and keeps the evidence. No vendor platform files the report, because ENISA offers manufacturers no submission API.
When does CRA Article 14 apply?
Article 14 reporting obligations apply from 11 September 2026. The CRA itself entered into force on 10 December 2024. Manufacturers should have their reporting workflow operational well before September 2026 to avoid scrambling when the first trigger event occurs.
Who has to report under Article 14?
Manufacturers placing products with digital elements on the EU market. This includes hardware with software, standalone software, and remote-data-processing components that are necessary for the product to function. Importers and distributors have downstream obligations but the primary Article 14 reporting duty sits with the manufacturer.
What is the Single Reporting Platform?
A reporting platform operated by ENISA that consolidates incident and vulnerability reports submitted under the CRA. It is the official channel for Article 14 reports. National CSIRTs also receive copies through this platform.
What happens if I miss the 24-hour deadline?
Article 64(2) of the CRA sets administrative fines of up to €15 million or 2.5% of total worldwide annual turnover for the preceding financial year, whichever is higher, for non-compliance with Article 14. The same tier covers Annex I and Article 13. Market surveillance authorities can also order corrective action, withdrawal or recall of the product.
Do I have to report low-severity vulnerabilities?
Only if they meet the trigger criteria: actively exploited (vulnerabilities) or severe (incidents). A low-severity vulnerability with no evidence of exploitation does not trigger Article 14. It still falls within the routine CVD process under Article 13.
How does CVD Portal help with Article 14?
CVD Portal tracks all three deadlines (24h, 72h, final report) with hard timers from the moment a triage event is flagged as Article 14-relevant. Receiving and tracking vulnerability reports is free. The Reporting plan adds the Article 14 deadline timers plus a guided workflow that pre-fills the report template from triage data, and an SRP-ready submission package for one-step manual filing to the ENISA Single Reporting Platform. ENISA provides no submission API at this stage, so automated filing follows once ENISA publishes an API.

Related

Article 14 is the reporting cascade on its own. For how it sits against the Article 13 duties, what is reportable in the first place, and when each obligation starts, see the CRA reporting obligations in full.

Make Article 14 boring before September 2026

CVD Portal tracks the 24h, 72h, and final-report deadlines automatically from the moment a triage event is flagged as Article 14-relevant. Receiving and tracking vulnerability reports is free. The Reporting plan adds the Article 14 deadline timers and an SRP-ready submission package for one-step manual filing to the ENISA Single Reporting Platform.