Article 14 deadline calculator
Enter when you became aware of an actively exploited vulnerability or a severe incident. The calculator shows when the early warning, the notification and the final report are due, in UTC and in your time zone, and lists the fields ENISA’s Single Reporting Platform asks for at each stage.
Information only, not legal advice. The calculator counts the deadlines the way the BitHive Reporting Desk counts them, as set out under “How the deadlines are counted”. Whether and how Article 14 applies to your product is a question for your own legal counsel.
The calculation runs entirely in your browser: what you enter is not sent to us, the page sends nothing while you use it, and it sets no cookie. It needs JavaScript (one script from this site); without it, the rules below still explain how each deadline is counted.
Your deadlines
Became aware:
| Report | Due by, UTC | Rule | |
|---|---|---|---|
| Early warning deadline passed | 24 hours after becoming aware (Article 14(2)(a))24 hours after becoming aware (Article 14(4)(a)) | ||
| Notification deadline passed | 72 hours after becoming aware (Article 14(2)(b))72 hours after becoming aware (Article 14(4)(b))Legal deadline, counted from when you became aware (CRA Art. 14). Until ENISA changes its platform, the Single Reporting Platform may show a different due time (ENISA SRP FAQ 26, 3 Oct 2026). | ||
| Final report deadline passed | 14 days after a corrective or mitigating measure is available (Article 14(2)(c))one month after the incident notification (Article 14(4)(c))Not known yet: enter when a measure became available.Not known yet: enter when you submitted the notification. |
The deadlines run continuously: weekends and public holidays are not excluded.
The calendar file is made in your browser and saved on your device; it is not sent to us.
The fields of ENISA’s Single Reporting Platform
Reports under Article 14 are submitted on ENISA’s Single Reporting Platform. It asks for its fields in this order and carries each stage’s fields into the next, where they stay editable. Draft your answers here and copy them across: nothing you type here leaves your browser, and reloading the page clears it.
The fields follow the kind of case chosen above. The platform is in English only.
- required at this stage
Chosen above: an actively exploited vulnerability or a severe incident.
- required at this stage
A short title of the report, at most 255 characters.
- required at this stage
What happened, in a few sentences, at most 4,000 characters.
4 Manufacturer
required at this stageThe platform fills this in from your organisation’s account.
- required at this stage
The Member States where the product is made available, and so the CSIRTs concerned.
- required at this stage
The product’s name, as you place it on the market.
- required at this stage
The affected versions, or their range.
- optional
Default, important or critical.
- optional
Class I or II, for an important product.
- optional
The product category in Annex III or IV, if one applies.
- optional
Yes or No: whether the product has reached the end of its support period.
- optional
The affected component, for example a library and its version.
- optional
Yes or No: whether a corrective or mitigating measure is expected shortly.
- optional
What users can do now.
- optional
How sensitive the information you report is.
- optional
How the vulnerability is exploited or the incident was carried out, where known.
- optional
The CVE identifier, if there is one.
- optional
The identifier in the EU Vulnerability Database, if there is one.
- required at this stage
General information about the product, the vulnerability and its exploitation.
- required at this stage
In UTC. Filled in from the calculator once you enter when the measure became available.
- required at this stage
The security update or other corrective or mitigating measure, and where users get it.
- required at this stage
How severe the vulnerability is.
- required at this stage
What impact it has.
- required at this stage
In UTC. Filled in from the calculator.
- optionalrequired at this stage
When the actively exploited vulnerability occurred, known or estimated, in UTC.
- optionalrequired if available
What is known about the malicious actor, if anything is.
- optional
Whether particularly exceptional circumstances apply. Asked with the notification only.
- optional
Why they apply.
- optional
Anything else the report should say.
- required at this stage
Yes, No or Unknown.
- required at this stage
The nature of the incident.
- required at this stage
The mitigation measures applied and ongoing.
- required at this stage
How severe the incident is.
- required at this stage
What impact it has.
- required at this stage
The type of threat, or the root cause, that probably triggered the incident.
- required at this stagerequired at this stage
In UTC. Filled in from the calculator. The platform’s current form labels this field “Date and time when the incident was detected (UTC time)”.
- required at this stage
When the incident began or took place, known or estimated, in UTC.
- required at this stage
An initial assessment of the incident.
- optionalrequired at this stage
The corrective or mitigating measures you have taken.
- optionalrequired at this stage
The measures users can take.
Fields and requirements as ENISA’s glossary of the platform gives them, version 1.4 of 1 October 2026. What the platform shows is what counts.
How the deadlines are counted
- The early warning is due 24 hours, and the notification 72 hours, after you became aware of the actively exploited vulnerability or the severe incident (Article 14(2)(a) and (b), 14(4)(a) and (b)). The hours count from the minute you became aware.
- For a vulnerability, the final report is due 14 days after a corrective or mitigating measure is available (Article 14(2)(c)), counted as 14 × 24 hours from that minute.
- For a severe incident, the final report is due one month after the notification (Article 14(4)(c)): at the same time of day on the same date a month later, or on the last day of that month when it has no such date, so 31 January gives 28 February, or 29 February in a leap year, and 31 March gives 30 April. The month is counted both in UTC and on Berlin’s clock, and the earlier of the two is the deadline. Where counting on the calendar of your own time zone ends earlier still, the calculator shows that time as well.
- The deadlines run continuously: weekends and public holidays are not excluded.
- Times are read on the clock of the time zone you choose. When the clocks go back and a time occurs twice, the earlier one counts, because it starts the deadline sooner. For a time the clocks skip when they go forward, the page shows how it is read.
Sources
- Regulation (EU) 2024/2847, the Cyber Resilience Act (opens in a new tab): Article 14 sets out the three reports and their deadlines.
- ENISA: glossary of the Single Reporting Platform (opens in a new tab): The platform’s fields, what each one asks for, and at which stage.
In the Reporting Desk
Upload your SBOM, or send each new one from your pipeline. Every hour, each monitored release is checked for actively exploited vulnerabilities listed by CISA KEV and ENISA EUVD, matched with OSV advisory data to its components from npm, PyPI, Maven, Go, NuGet, RubyGems, crates.io and Debian; when a monitored component is affected, a case opens with its clock already running. In the BitHive Reporting Desk, each deadline runs from the point the law sets – the moment you became aware, the submission of an earlier report or a request from the authority – as recorded in the case. Each report starts as a draft with the details the authority asks for, and the people you name are alerted before every deadline. If nobody has opened or acknowledged the case two hours after its clock started, your named backup is alerted as well. See how the Reporting Desk works
| This page | In the Reporting Desk | |
|---|---|---|
| Who is told | You, here and now | The people you name, by e-mail, Slack, Microsoft Teams or webhook. If nobody has opened or acknowledged the case two hours after its clock started, your named backup is alerted as well |
| The report | The list of what the authority asks | A draft with the details the authority asks for, for you to complete and submit, with the submission time recorded |
| Proof | Your entries stay in your browser and are not stored | A timestamped record of every step, decision and submission, ready to export |
| Over time | A single incident, calculated now | Every case with its deadlines and reminders, until it is closed |
General information, not legal advice.
Start free 14-day trial