CRA reporting timeline: 24 hours, 72 hours and the final report

The Cyber Resilience Act's reporting deadlines are elapsed time from awareness — 24 hours for the early warning and 72 hours for the notification — followed by a final report whose trigger differs: 14 days after a fix is available for exploited vulnerabilities, one calendar month after the notification for severe incidents.

By the Vellaci teamPublished Updated 7 min readOperational guidance, not legal advice

Share:LinkedInXE-mail

Key facts

Clock start
The moment the manufacturer becomes aware (recorded with timezone)
Early warning
+24 h
Notification
+72 h
Final report (vulnerability)
Fix available + 14 days
Final report (incident)
Notification + 1 calendar month
Weekends and holidays
Count. The 24 h and 72 h periods never pause; plan the day- and month-based final reports for the unextended date
Looking for the regulation's dates?
Entry into force, 11 September 2026, 11 December 2027 and the transitional rules are in the CRA timeline guide

Two case types, two final-report triggers

Both actively exploited vulnerabilities and severe incidents share the 24-hour early warning and 72-hour notification from awareness. They differ on the final report.

  • Vulnerability: final report no later than 14 days after a corrective or mitigating measure becomes available. Until such a measure exists, no final-report timer runs — but the vulnerability-handling duty to remediate without delay does.
  • Incident: final report within one month after the 72-hour notification. One month is a calendar month, not 30 days: a notification submitted on 31 January leads to a final report due by 28 (or 29) February; one submitted on 15 March is due by 15 April.

Worked example 1 — exploited vulnerability

Awareness: Monday 5 October 2026, 09:15 CEST (Europe/Brussels), confirmed by the security lead after a customer's incident responder shares indicators matching a KEV-listed CVE in a shipped component.

Early warning due: Tuesday 6 October 2026, 09:15 CEST.

Notification due: Thursday 8 October 2026, 09:15 CEST.

Fix released: Tuesday 20 October 2026, 18:00 CEST → final vulnerability report due Tuesday 3 November 2026, 18:00 CET. Note the daylight-saving change on 25 October: the deadline stays at 18:00 local time, which is one hour later in UTC than it would have been in CEST. Compute in the organisation's IANA timezone, never in fixed offsets.

Worked example 2 — severe incident

Awareness: Friday 29 January 2027, 17:40 CET, when the on-call engineer confirms that the update server distributed a tampered package to devices in three Member States.

Early warning due: Saturday 30 January 2027, 17:40 CET — a Saturday; the runbook's deputy submits.

Notification submitted: Sunday 31 January 2027, 16:00 CET (within the 72-hour window ending Monday 1 February, 17:40 CET).

Final report due: one calendar month after the notification — Sunday 28 February 2027, 16:00 CET. Adding 30 days would have produced 2 March, which is late.

Worked example 3 — no fix yet

Awareness of exploitation on 12 May 2027 at 08:00 CEST; early warning and notification follow at 08:00 on 13 and 15 May. The corrective measure is a firmware update that ships on 30 June 2027 at 10:00 CEST. The final report is due 14 July 2027, 10:00 CEST. Between 15 May and 30 June no final-report timer runs, but the 72-hour notification should already describe mitigations users can apply, and a mitigating measure (a configuration workaround published on 20 May) would itself have started the 14-day clock — which is why the record must state precisely which measure was 'available' and when.

The 'unless already provided' nuance

Article 14 says the 72-hour notification is due 'unless the relevant information has already been provided'. If your early warning already contained everything the notification requires, you may not need a separate submission — but in practice the initial assessment and the measures sections are rarely complete at hour 24. Treat the notification as an update to the early warning, and keep both as frozen revisions so the sequence is auditable.

Timeline at a glance

MomentVulnerability caseIncident case
T0 — awarenessRecorded with timezone and confirming personRecorded with timezone and confirming person
T0 + 24 hEarly warningEarly warning (incl. whether malicious acts suspected)
T0 + 72 hNotificationNotification
Fix available (F)Starts the 14-day final-report timer—
F + 14 daysFinal report—
Notification + 1 calendar month—Final report
ContinuousInform impacted users; remediate; updateInform impacted users; contain; remediate

Several products, one event

When one exploited component affects several products, awareness is a single moment and the clocks are shared: one early warning describing all affected products and versions, one notification, and — for the vulnerability case — a final report 14 days after the corrective measure for the last affected product ships, or separate final reports per product if fixes arrive far apart and you prefer to close each thread. Keep one case with all products linked so the Member States list and the measures section stay consistent across submissions.

After hours and across borders

Awareness at 17:00 on a Friday puts the early warning at 17:00 on Saturday. The runbook therefore needs a deputy for the assigned representative, platform credentials held by at least two people, and a decision rule for who confirms awareness when the security lead is unreachable. Teams split across time zones should agree the organisation's reference timezone in advance and record every timestamp with its offset; the regulation does not prescribe a timezone, but inconsistency inside a case is what invites questions.

Weekends, public holidays and Regulation 1182/71

Article 14 does not exclude weekends or public holidays, and the 24-hour and 72-hour periods are expressed in hours: they run continuously, so awareness on a Friday evening puts the early warning on Saturday evening. Regulation (EEC, Euratom) No 1182/71, which sets the EU's general rules on periods, dates and time limits, confirms that periods include public holidays, Saturdays and Sundays unless they are expressly excepted or expressed in working days (Article 3(3)).

The final reports are different in form: fourteen days after a corrective measure and one month after the notification are periods expressed in days and months. For such periods Article 3(4) of Regulation 1182/71 provides that, where the last day is a public holiday, Saturday or Sunday, the period ends with the expiry of the last hour of the following working day, and Article 3(1)–(2) counts whole days rather than timestamp to timestamp. Neither the CRA nor ENISA guidance has confirmed how these rules apply to Article 14, and public holidays differ between Member States.

The defensible practice is to plan for the unextended date. Vellaci's deadline engine and the free calculator do exactly that: hours are absolute durations from the recorded awareness time, and days and months are calendar periods computed in the organisation's timezone from the source timestamp, with no weekend or holiday extension. If a final report is submitted on the following working day, record the reasoning in the case.

Use the calculator

The free CRA deadline calculator on this site uses the same versioned deadline engine as the Vellaci product, including calendar-month arithmetic and timezone handling across daylight-saving transitions. Inside Vellaci, the same engine runs as a background job that persists each deadline with the rule version and source timestamp that produced it, so a later change of awareness time recalculates everything with an audit trail.

Frequently asked questions

What if awareness turns out to be earlier than first recorded?
Correct the awareness time with a reason; the deadlines recalculate and the change is audited. Report on the corrected timeline and say so in the notification — a documented correction is defensible; an undocumented one is not.
Do we count hours or working days?
Hours. 'Within 24 hours' is elapsed time.
Which timezone applies?
The regulation does not prescribe one. Compute in the organisation's timezone for operations and show UTC alongside for the record; be consistent within a case.
Are weekends and public holidays included in the CRA reporting deadlines?
Yes. The 24-hour early warning and the 72-hour notification run through weekends and public holidays without any pause. For the final reports, which are counted in days or months, Regulation 1182/71 may move an end date that falls on a weekend or public holiday to the next working day, but that has not been confirmed for Article 14 — plan for the unextended date and staff the runbook for weekends.
Does the 24-hour clock start at the exact minute of awareness?
Treat it that way. Regulation 1182/71 would not count the hour in which an event occurs, which could add up to an hour, but relying on that margin is hard to defend. Record the awareness timestamp to the minute with its timezone and compute from it.
Where are the CRA's own application dates?
This guide covers the Article 14 reporting clocks. The regulation's dates — entry into force on 10 December 2024, notified-body rules from 11 June 2026, reporting in force since 11 September 2026, full application on 11 December 2027 and the transitional rules — are in the CRA timeline guide.

From requirement to evidence

What the obligations in this guide mean for an engineering, security or compliance team, the Vellaci workflow that supports each one, and the records it leaves. The full map for every CRA obligation is on the CRA compliance software page.

How to read this. Official requirement summarises the text of Regulation (EU) 2024/2847 with its reference. What your team does is Vellaci’s operational interpretation, not legal advice. Vellaci workflow and Evidence describe what the product does today. Methodology · reviewed 2026-10-05.

  1. Report actively exploited vulnerabilities

    Article 14(1)–(2)Applies since 11 Sep 2026
    Official requirement
    Notify any actively exploited vulnerability contained in the product to the CSIRT designated as coordinator and to ENISA via the single reporting platform: early warning within 24 hours of becoming aware, notification within 72 hours, final report no later than 14 days after a corrective or mitigating measure is available.
    What your team does (interpretation)
    Decide who confirms awareness and reportability, record when they did it and in which timezone, and have the content of each stage ready before the clock runs out.
    Vellaci workflow
    Explicit CRA review on every finding, reporting case with server-computed 24 h / 72 h / final-report deadlines, staged and prefilled forms. How it works
    Evidence produced
    • Reportability decision with rationale and reviewer
    • Confirmed awareness time and timezone
    • Frozen revision of each submitted stage with SRP reference
  2. Report severe incidents

    Article 14(3)–(4)Applies since 11 Sep 2026
    Official requirement
    Notify any severe incident having an impact on the security of the product to the coordinator CSIRT and ENISA via the single reporting platform: early warning within 24 hours of becoming aware, notification within 72 hours, final report within one month after the notification.
    What your team does (interpretation)
    Keep incidents separate from vulnerabilities — the final-report trigger differs — and answer the 'severe incident' question explicitly, with a named person and a reason.
    Vellaci workflow
    Incident records with confirmed awareness time and severe-incident review, opening a reporting case with the incident timeline. How it works
    Evidence produced
    • Incident record with impact, affected versions and Member States
    • Severe-incident decision with rationale
    • Final report and its submission record
  3. Inform impacted users

    Article 14(8)Applies since 11 Sep 2026
    Official requirement
    After becoming aware of an actively exploited vulnerability or a severe incident, inform the impacted users — and where appropriate all users — about it and about risk-mitigation and corrective measures they can deploy, where necessary in a structured, machine-readable format.
    What your team does (interpretation)
    Draft the user communication from the same facts as the notification, and keep the version that was actually sent.
    Vellaci workflow
    No dedicated drafting tool: the communication as sent is filed in the evidence vault and linked to the incident or reporting case, next to the corrective measure. How it works
    Evidence produced
    • Sent user communication with date, linked to the case
    • Corrective measure or fixed version it refers to

Compute your own reporting deadlines.

Enter an awareness time and timezone; get the early warning, notification and final-report dates with calendar-month arithmetic and daylight-saving handling.