CRA Article 14 deadlines with worked examples
Last verified: 2026-11-20.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-20.
Short answer
- Actively exploited vulnerability: early warning without undue delay and in any event within 24 hours of becoming aware; vulnerability notification within 72 hours of becoming aware; final report no later than 14 days after a corrective or mitigating measure is available (CRA Art. 14(2)).
- Severe incident: early warning within 24 hours of becoming aware; incident notification within 72 hours of becoming aware; final report within one month after you submit the 72-hour notification (CRA Art. 14(4)).
- The 72 hours run from becoming aware, not from the early warning. ENISA's platform currently shows its 72-hour due time 48 hours after you submit the early warning (CRA Art. 14(2)(b), 14(4)(b); ENISA SRP FAQ 26).
- Where: ENISA's Single Reporting Platform. The report goes to the CSIRT designated as coordinator in the Member State of your main EU establishment and is at the same time accessible to ENISA (CRA Art. 14(7)).
- Since when: 11 September 2026, also for products placed on the market before 11 December 2027 (CRA Art. 69(3), 71(2)).
When the clock starts
Every clock except the final report starts when you become aware. In the Commission's reading, you should assess a suspicious event immediately, and you become aware when, after that initial assessment, you have a reasonable degree of certainty that a vulnerability in your product is being actively exploited or that a severe incident has compromised its security; the emphasis is on prompt action (Guidance, points 211–214). The guidance is not binding (Guidance, point 8). Our conservative reading: if you are unsure, use the earliest plausible time.
How we count
Article 14 does not say how to count hours, days or months, and the reporting section of the Commission guidance (points 209–221) does not address it (CRA Art. 14; Guidance). The examples below use our conservative reading, which is also what the Shieldbook deadline tool computes:
- all times in UTC;
- 24 and 72 hours are elapsed hours, so nights, weekends and public holidays count;
- 14 days are 14 × 24 hours;
- one month ends on the same day and time of the next calendar month; if that month is shorter, on its last day;
- no deadline is moved because it falls on a weekend or holiday.
Example 1: actively exploited vulnerability
| Step | Time (UTC) | How it is computed | Article |
|---|
| You become aware | Fri 4 Dec 2026, 16:30 | — | — |
| Early warning due | Sat 5 Dec 2026, 16:30 | aware + 24 h | 14(2)(a) |
| Vulnerability notification due | Mon 7 Dec 2026, 16:30 | aware + 72 h | 14(2)(b) |
| Patch available | Thu 10 Dec 2026, 09:00 | — | — |
| Final report due | Thu 24 Dec 2026, 09:00 | patch + 14 days | 14(2)(c) |
The Saturday deadline and the 24 December deadline stay where they are.
Example 2: severe incident, month clamped
| Step | Time (UTC) | How it is computed | Article |
|---|
| You become aware | Thu 28 Jan 2027, 09:00 | — | — |
| Early warning submitted | Thu 28 Jan 2027, 18:00 | — | — |
| Early warning due | Fri 29 Jan 2027, 09:00 | aware + 24 h | 14(4)(a) |
| Incident notification submitted | Sat 30 Jan 2027, 14:00 | — | — |
| Incident notification due | Sun 31 Jan 2027, 09:00 | aware + 72 h | 14(4)(b) |
| Final report due | Sun 28 Feb 2027, 14:00 | submission + 1 month; February 2027 has no 30th, so the last day of February | 14(4)(c) |
Two points from this example:
- The final report counts from when you submitted the notification, not from its deadline. Had you submitted at the last moment, Sun 31 January 09:00, the final report would be due Sun 28 February 09:00.
- In its current release, ENISA's platform would show the 72-hour notification as due Sat 30 January 18:00, 48 hours after the early warning, which is 15 hours before the legal deadline. ENISA says it will change this to count from the time you became aware (ENISA SRP FAQ 26).
Where you submit
You submit one notification per event on ENISA's Single Reporting Platform, operational since 11 September 2026 (ENISA SRP FAQ 4, 8). Your main EU establishment is where decisions on your products' cybersecurity are mainly taken, or else where you have the most EU employees; without one, Article 14(7) sets the order: authorised representative, importer, distributor, then most users (CRA Art. 14(7)).
Fines and small companies
Breaches of Article 14 can be fined up to EUR 15 000 000 or 2.5% of total worldwide annual turnover for the preceding financial year, whichever is higher, under rules each Member State lays down (CRA Art. 64(1)–(2)). Manufacturers that are micro or small enterprises are not fined for missing the 24-hour early-warning deadline; the duty remains, and the 72-hour and final-report deadlines are not covered (CRA Art. 64(10)(a), as corrected on 2 July 2025).
To compute these deadlines with an AI assistant, add Shieldbook to Claude or connect the Shieldbook MCP server (https://shieldbook.ppftec.com/mcp) and use the cra_reporting_deadlines tool; it works without an account.
FAQ
Does the 72-hour deadline count from the early warning?
No. Both the 24-hour and the 72-hour deadlines count from becoming aware (CRA Art. 14(2)(a)–(b), 14(4)(a)–(b)). ENISA's platform currently displays a 72-hour due time 48 hours after the early warning; the legal deadline is unchanged (ENISA SRP FAQ 26).
Does a deadline on a weekend or public holiday move to the next working day?
Article 14 does not say so. Our conservative reading is that it does not move, as in both examples above (CRA Art. 14(2), 14(4)).
Do I report exploitation I knew about before 11 September 2026?
No. In the Commission's reading, the CRA does not require retroactive reports; but if you first become aware of active exploitation after that date, you must report it (Guidance, point 217).
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Art. 3(42), 14, 15, 16, 64, 69 and 71 read 2026-11-20.
- Corrigendum to Regulation (EU) 2024/2847, Art. 64(10), OJ L 2025/90555, 2.7.2025. Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32024R2847R(02). File read: https://publications.europa.eu/resource/cellar/696c22ec-56e1-11f0-a9d0-01aa75ed71a1.0006.01/DOC_1 (2026-11-20).
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act), Communication C/2026/6013, OJ C, 17.11.2026, not binding (point 8). Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202606013. File read (OJ C PDF via the Publications Office): https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8 and 209–224 read 2026-11-20.
- ENISA, CRA Single Reporting Platform FAQ, updated 17 November 2026 (FAQ 4, 8 and 26): https://www.enisa.europa.eu/topics/product-security/single-reporting-platform-srp/frequently-asked-questions (2026-11-20).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.