Article 14 Notification Template Builder
Draft each Article 14(2) stage for an actively exploited vulnerability. The stages are the 24-hour early warning, the 72-hour vulnerability notification and the final report. Fill in your product details, exploitation status and mitigation actions, then copy the text into the ENISA Single Reporting Platform.
Last updated 25 October 2026
Key takeaways
- An Article 14(2)(a) early warning must indicate, where applicable, the Member States where the product is available. The 72-hour notification and the final report carry the detail.
- Manufacturers submit Article 14 notifications on the ENISA Single Reporting Platform, using the end-point of their coordinating CSIRT.
- An early warning does not require an assigned CVE ID within the initial 24-hour reporting window.
- Article 14 notifications are shared between CSIRTs and ENISA but not published, and ENISA lists a fixed vulnerability in the European vulnerability database only in agreement with the manufacturer.
Select the notification stage. Each stage has different content requirements under Article 14.
Manufacturer details
Product and vulnerability
Exploitation status
Impact
Mitigation
CRA early warning, Article 14(2)(a) Submitted: 2026-11-22 12:56:44 UTC ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1. Notifying manufacturer ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Company: [Company name] Contact: [Contact name] Email: [Contact email] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2. Affected product ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Product name: [Product name] Affected version(s): [Version] CVE identifier: Pending assignment ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 3. Exploitation status ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Actively exploited: Yes ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 4. Impact assessment ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Estimated affected users: [Number or estimate] Member States where the product is available: [Member States] ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 5. Initial mitigation ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Immediate actions taken: [Describe any immediate actions] A vulnerability notification follows within 72 hours of becoming aware of the exploitation. ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Declaration ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ [Company name] confirms that this notification is submitted in compliance with Article 14(2)(a) of Regulation (EU) 2024/2847 (Cyber Resilience Act).
Submit it on the ENISA Single Reporting Platform (SRP), through the end-point of the CSIRT designated as coordinator in your Member State. The final report is due 14 days after a fix or mitigation is available. CVD Portal records each stage you file and alerts you before a deadline passes.
Frequently asked
What information must an Article 14 early warning include?+
Article 14(2)(a) asks for little. The early warning must indicate, where applicable, the Member States where you know the product is available. The detail comes later. The 72-hour vulnerability notification under Article 14(2)(b) gives general information on the product, the nature of the exploit and the vulnerability, the corrective or mitigating measures, and how sensitive you consider the information. The final report under Article 14(2)(c) describes the vulnerability with its severity and impact, any known malicious actor, and the security update. The Single Reporting Platform form has its own fields on top of this.
Where do I submit the Article 14 notification?+
Article 14(7) requires submission on the ENISA Single Reporting Platform, using the end-point of the CSIRT designated as coordinator in the Member State of your main establishment. ENISA can access the notification at the same time. The platform has been operational since 11 September 2026.
Do I need a CVE ID before submitting?+
No. A CVE ID is not required for the early warning. The 24-hour early warning deadline means you will often not have a CVE assigned yet. You can submit with 'CVE pending' and add the CVE to the 72-hour vulnerability notification if one is assigned by then.
Is the notification published?+
No, but it is shared. The coordinating CSIRT passes it to the CSIRTs of the Member States where you said the product is available, unless it delays that on cybersecurity grounds under Article 16(2). After a fix is available, ENISA adds the vulnerability to the European vulnerability database only in agreement with you, under Article 17(5). Under Article 14(8), a CSIRT may inform your users itself if you do not inform them in time.
Other free CRA tools
Ready to automate your CVD programme?
CVD Portal integrates all these tools and handles your Article 13 and 14 obligations automatically.
Create my free CVD portal →Create your free CVD portal →