Article 14 reporting is live: what the 24-hour clock asks of you
Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents within 24 hours, for products already on the market too.
The first CRA duties are live. Since 11 September 2026, a manufacturer that becomes aware of an actively exploited vulnerability in its product, or a severe incident that affects the product’s security, has to notify it within 24 hours (Art. 14).
This applies to every product with digital elements in scope, including products placed on the market before the rest of the regulation applies on 11 December 2027 (Art. 69(3)). If you have connected products on sale in the EU today, the clock already applies to them.
The Commission’s guidance of July 2026 adds that it carries on after a product’s support period has ended (paragraph 210). It isn’t retroactive: exploitation you knew about before 11 September needn’t be reported, but anything you learn of now must be, however old the product (paragraph 217).
The three deadlines
Reports go through the single reporting platform to the CSIRT designated as coordinator in the member state of your main establishment, and to ENISA.
| Report | Exploited vulnerability | Severe incident |
|---|---|---|
| Early warning | 24 hours after you become aware | 24 hours after you become aware |
| Notification | 72 hours after you become aware | 72 hours after you become aware |
| Final report | 14 days after a fix or mitigation is available | One month after the notification |
Every deadline runs from the moment you become aware. That makes the time you learned something a piece of evidence in itself. A log that records when a report arrived, who triaged it and when it was judged exploited is what lets you show you met the clock.
You also have to tell the users affected, and where needed tell them how to mitigate it (Art. 14(8)). The Commission’s guidance reads this as risk-based: it doesn’t have to mean a public announcement (paragraphs 219 to 221).
When the clock starts
The guidance puts the moment you become aware at the point where an initial assessment gives you “a reasonable degree of certainty” that the vulnerability is being exploited (paragraph 213). A vulnerability in a component that isn’t exploitable in your product isn’t reportable (paragraph 218).
So the record should show both: when a report arrived, and when your assessment reached that degree of certainty. It also shows why a report you didn’t make wasn’t due.
Using the reporting platform
ENISA’s single reporting platform went live on 11 September 2026. A few practical points from its FAQ:
- You need an EU Login account with two-factor authentication to register as the person who submits. ENISA suggests registering only when you need to submit. We’d set up accounts for whoever would submit now, so the first hour of a 24-hour clock isn’t spent on a login.
- There’s no API yet. Reports are entered in a web form, so tooling can prepare the content but not send it.
- If the platform is down, ENISA says to submit once it’s back. You can contact your CSIRT directly in the meantime, but the notification still has to go through the platform.
What to have in place before the first one
- A way to become aware. Published contact details, such as an email address, for vulnerability reports to reach you, automated monitoring of the components in your SBOM, and a route from support and field teams into security.
- A decision record. “Actively exploited” is a judgement. Write down who makes it, on what evidence, and record each call with its time.
- Named people. Who drafts, who approves and who submits, with cover for weekends and holidays. The 24 hours are calendar time, not working hours.
- Prepared content. Product identification, the member states where it is available, and templates for each stage, so the early warning process is easy to complete within the deadline, ideally taking just minutes.
- A rehearsal. Run one past incident through the process end to end and time it.
Where this fits in the file
We appreciate many manufacturers will not yet have suitable product/process documentation in place, but this obligation under the CRA is a great time to get started.
The reporting process belongs in the vulnerability handling part of your technical documentation (Annex VII (2)), and every report you make belongs in the product’s record. A notification that cannot be traced back to the vulnerability log and the release that fixed it is hard to defend later.
Reach out for help with creating your process.
Talk to us
Book a 30-minute call
Tell us what the product does and where you sell it. We'll talk through what the CRA is likely to ask of it, and whether an assessment is worth doing.
Book a call or email [email protected]
Useful to have to hand
- What the product is and how it connects
- Where you sell it, and who places it on the EU market
- How often you release software or firmware
- Any date you're working towards