Active Exploitation and Incident Reporting - 24h, 72h, and 14-Day Obligations
Since 11 September 2026, CRA Article 14 has required manufacturers to send a 24-hour early warning, a 72-hour notification and a final report to the coordinator CSIRT and ENISA for each actively exploited vulnerability or severe incident.
What are the three Article 14 reporting deadlines?
Article 14 establishes a three-stage notification process triggered by active exploitation of a vulnerability or a severe security incident:
| Stage | Deadline | What to Report |
|---|---|---|
| Early Warning | 24 hours | Notification that exploitation is occurring; basic product and vulnerability information |
| Vulnerability Notification | 72 hours | Full notification including CVSS score, affected versions, initial mitigations |
| Final Report | 14 days after a fix is available (vulnerability), or one month after the 72-hour notification (incident) | Complete analysis, root cause, patch or workaround, supply chain impact |
The first two deadlines are calculated from the moment the manufacturer becomes aware of the active exploitation or incident - not from when exploitation began. The final report runs on a different clock, and this is the detail most summaries get wrong. For an actively exploited vulnerability, Article 14(2)(c) gives you 14 days from the moment a corrective or mitigating measure is available, not from awareness. For a severe incident, Article 14(4)(c) gives you one month from the submission of the 72-hour incident notification. The full legal text is set out in Article 14 of Regulation (EU) 2024/2847 on EUR-Lex.
When does a manufacturer 'become aware'?
Every Article 14 deadline runs from the moment the manufacturer becomes aware, and the Regulation does not define that moment. Commission guidance C(2026) 5252 does. On detecting a suspicious event, or on a third party such as a researcher, customer, authority or media organisation bringing something to its attention, the manufacturer should assess it immediately. Awareness arises when, after that initial assessment, there is a reasonable degree of certainty that a vulnerability contained in the product is being actively exploited, or that a severe incident has occurred and has compromised the security of the product.
Receiving a report therefore does not by itself start the clock, and neither does an unexamined suspicion. A short triage window sits in front of the 24 hours. It is not open-ended, and the guidance stresses prompt action to carry out the initial assessment, particularly where the vulnerability may pose a significant risk.
The Commission deliberately aligned this reading with recital 31 of Implementing Regulation (EU) 2024/2690 under NIS2 and with Section II(A) of the EDPB guidelines on personal data breach notification under the GDPR, so that a manufacturer subject to several regimes can apply one awareness standard. The guidance is non-binding, and only the Court of Justice of the European Union can give an authoritative interpretation.
What triggers Article 14 reporting?
Two conditions trigger Article 14 notification:
- Active exploitation - A vulnerability in your product is being actively exploited in the wild. This means there is evidence of real-world attacks using the vulnerability, not just proof-of-concept code.
- Severe incident - An incident that affects, or can affect, the ability of the product to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led, or can lead, to malicious code in the product or in a user's network and information systems (Article 14(5)).
Not triggered by: Theoretical vulnerabilities, vulnerabilities with no known exploitation, low-severity bugs, or normal vulnerability reports received through your CVD programme that are not actively exploited.
Where do you submit an Article 14 report?
Notifications must be submitted to the CSIRT designated as coordinator in the member state where you have your main establishment, and to ENISA. Each EU member state designates a coordinator CSIRT for this purpose. Without a main establishment in the EU, the coordinator is the CSIRT of the Member State where your authorised representative is established, then where your importer is, then where your distributor is, and otherwise where the product has the most users (Article 14(7)).
Every notification goes through the Single Reporting Platform that ENISA runs, under Article 14(7). The platform is live. The Single Reporting Platform guide shows registration and each submission step.
You file once. Under Article 16(2), the coordinator CSIRT passes the notification on through the platform, without delay, to the CSIRTs of the other Member States where you said the product is available. The CSIRT can delay that step on justified cybersecurity grounds, in particular when you ask for it because the information is sensitive.
- Germany: BSI (Federal Office for Information Security)
- France: ANSSI
- Netherlands: NCSC-NL
- Sweden: NCSC-SE
- Spain: INCIBE-CERT
CVD Portal can prepare Article 14 notifications in the required format and alert you when deadlines are approaching. A person files them on the Single Reporting Platform.
The 24-Hour Early Warning
The 24-hour early warning is not a full technical report - it is a rapid notification that exploitation is occurring.
- Product name and affected version(s)
- A brief description of the vulnerability
- Initial mitigation actions taken (if any)
You do not need to have a root cause analysis or patch ready at this stage. Speed of notification is the priority.
The 72-Hour Full Notification
Within 72 hours of becoming aware of active exploitation, you must submit the vulnerability notification. Article 14(2)(b) asks for, as available:
- General information about the product concerned
- The general nature of the exploit and of the vulnerability
- Corrective or mitigating measures taken, and measures that users can take
- Where applicable, how sensitive you consider the information to be
Optional details that help the CSIRT include a CVSS score and vector, a CVE identifier, and the affected versions and configurations.
72 hours is a very tight window for a complete analysis. This means your incident response process must be able to move very quickly when an active exploitation is confirmed.
The Final Report
The final report closes the case with ENISA and the coordinating CSIRT. Its deadline depends on which trigger you are reporting. For an actively exploited vulnerability, Article 14(2)(c) gives you 14 days from the moment a corrective or mitigating measure is available. For a severe incident, Article 14(4)(c) gives you one month from the submission of the 72-hour incident notification. Article 14(2)(c) asks for at least a description of the vulnerability with its severity and impact, information on any malicious actor where available, and details of the security update or other corrective measure. Article 14(4)(c) asks for a detailed description of the incident with its severity and impact, the likely threat type or root cause, and the applied and ongoing mitigation measures. Good practice adds:
- Complete remediation details (patch release, advisory publication)
- CSAF advisory (if applicable)
- Supply chain coordination actions taken
- Steps taken to prevent recurrence
- Lessons learned
If the case is still open when your clock runs out, submit what you have and explain what remains under investigation. Separately, under Article 14(6) the coordinating CSIRT that received your notification can request an intermediate report on status updates at any point between the stages.
Must you inform your users?
Yes. Under Article 14(8), after you become aware of an actively exploited vulnerability or a severe incident, you must inform the impacted users, and where appropriate all users. Tell them about the vulnerability or incident and, where necessary, about the risk mitigation and corrective measures they can apply. Where appropriate, give this information in a structured, machine-readable format, such as a CSAF advisory.
This duty runs next to the reports to the CSIRT and ENISA. If you do not inform users in time, the notified CSIRTs can inform them instead.
What are the Article 14 supply chain obligations?
If a vulnerability is in a component you integrate from a third party, you remain responsible for the Article 14 notification for your product.
Article 13(6) also requires you to report a vulnerability that you identify in an integrated component, including an open-source component, to the person or entity that manufactures or maintains it. Good practice is to agree remediation timelines with that party and to describe the supply chain dimension in your Article 14 notifications.
Do importers and distributors report under Article 14?
Article 14 binds the manufacturer. The manufacturer submits the early warning, the notification and the final report.
Importers and distributors have a shorter duty. When they become aware of a vulnerability in a product, they must inform the manufacturer without undue delay, under Article 19(5) for importers and Article 20(4) for distributors. Where the product presents a significant cybersecurity risk, they must also immediately inform the market surveillance authorities of the Member States where they made it available.
Under Article 21, an importer or distributor counts as the manufacturer when it places the product on the market under its own name or trademark, or makes a substantial modification to a product already on the market. It then carries Articles 13 and 14 in full.
Does the obligation apply retroactively or after support ends?
No to the first and yes to the second. Commission guidance C(2026) 5252 confirms that Article 14 applies from 11 September 2026 to all products with digital elements in scope, including products placed on the market before 11 December 2027, and that the reporting obligations continue after a product is no longer supported. Vulnerability handling under Annex I Part II behaves differently and stops with the support period.
There is no retroactive reporting. A manufacturer is not required to report active exploitation it had already become aware of before 11 September 2026. Where a vulnerability was known before that date but its active exploitation was not, either because none had occurred or because the manufacturer had not learned of it, and exploitation occurs or comes to light after that date, the vulnerability is reportable.
A vulnerability originating in an integrated third-party component is reportable only where it is actively exploited in your product. Where the vulnerable code is unreachable, or exploitation has not occurred in your product, no mandatory report arises. Voluntary notification under Article 15 remains available, the Annex I Part II handling requirements still apply, and Article 13(6) still requires the vulnerability to be reported upstream to whoever maintains the component.
How do you prepare to meet the 24-hour deadline?
The 24-hour clock starts when you become aware of active exploitation, so the preparation must be in place before an event. Four measures close most of the gap.
- Name who decides. Give one role, such as the PSIRT lead or the on-call incident lead, the authority to declare that exploitation is active and to start the early warning. An approval chain that needs an executive at night is a common reason for a missed deadline.
- Prepare the reports. Draft the early warning and the 72-hour notification in advance. Register on the Single Reporting Platform, confirm which CSIRT is your coordinator under Article 14(7), and test the accounts before you need them.
- Watch for exploitation. Logs, telemetry and threat intelligence show exploitation that nobody reports to you.
- Send disclosure reports to triage at once. Your vulnerability intake is often the first place you hear of exploitation. Ask reporters whether they see active exploitation, and send each yes straight to the person on call.
Article 14 depends on Article 13. Without a published disclosure policy and a monitored intake channel, you can become aware late, after the exploitation is already public. The Article 14 timeline tool shows each deadline from a given awareness time.
Work through Article 14 for each product in one CRA workspace.
Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.
Frequently asked
Does Article 14 apply to every vulnerability I discover?+
No. Article 14 only applies when there is active exploitation of a vulnerability in your product or a severe security incident. Vulnerabilities discovered through your CVD programme that are not being actively exploited are handled under Article 13, not Article 14.
What if I can't complete the 72-hour report on time?+
Article 14(2)(b) asks for the information as available. If a full technical analysis is not possible within 72 hours, submit what you have and note that the report is preliminary. Document your reasons for any delay.
How do I know if exploitation is 'active'?+
Active exploitation means there is credible evidence that attackers are using the vulnerability in real attacks. This includes: reports from customers of successful attacks, detection by threat intelligence services, exploitation code seen in the wild, or confirmation from a national CSIRT. A publicly available PoC without confirmed exploitation does not automatically trigger Article 14, but the risk level increases significantly.
Does Article 14 apply to vulnerabilities found by internal security testing?+
No. Article 14 is triggered by active exploitation or severe incidents, not by internally discovered vulnerabilities. Internal vulnerability management is covered by Article 13 and Annex I. Article 14 is specifically about responding to real-world attacks.
What is the penalty for missing an Article 14 deadline?+
Missing Article 14 notification deadlines can result in fines up to €15 million or 2.5% of global annual turnover. More immediately, failure to notify can result in corrective measures and increased scrutiny from national market surveillance authorities.
Need a CVD policy for Article 14?
Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.