From 11 September 2026, anyone who makes an IP camera, a home router, an industrial PLC or connected software must report actively exploited flaws within 24 hours. Reports go to ENISA and to their national CSIRT. This is Article 14 of the Cyber Resilience Act. It is the first binding duty of the law, and it arrives fifteen months before everything else.
What Article 14 actually requires
The Cyber Resilience Act, Regulation (EU) 2024/2847, takes full effect on 11 December 2027. But Article 14, the duty to report, applies from 11 September 2026. It covers “manufacturers of products with digital elements”. This means any hardware or software that connects, directly or not, to a device or network.
The duty applies in two cases:
- Actively exploited vulnerability: there is solid evidence that an attacker has used the flaw in a system without the owner’s permission.
- Severe incident: a security event that hits the maker’s development, production or maintenance work in a way that raises the risk for users.
There are three deadlines, and this is where many sources oversimplify:
| Stage | Deadline | What it contains |
|---|---|---|
| Early warning | 24 hours from awareness | Minimal notification: an exploited vulnerability exists, which member states the product is sold in. No root cause or fix required yet |
| Notification | 72 hours from awareness | General nature of the vulnerability or incident, initial assessment, corrective measures taken or available |
| Final report | 14 days from when a corrective measure becomes available (vulnerabilities) — one month from the 72-hour notification (severe incidents) | Full description, severity, impact, remediation applied |
Here is the detail most guides get wrong. For a vulnerability, the final report deadline does not start when the flaw is found. It starts when a fix is available. A team that sets a reminder for “day 14 after awareness” risks filing an empty report for a deadline that does not exist yet. Or it may miss the real deadline if the fix arrives late.
Who is actually affected: not just smart-home gadgets
The common story about the CRA is that “it is about smart home devices”. That is only partly true. And for a professional Italian reader, it is the least interesting part.
Video surveillance. Connected IP cameras are “Important Class I products” in Annex III. This is the same risk level as smart locks, baby monitors and alarm systems. The law’s recitals name them as higher-risk consumer products. An installer or system integrator who sells cameras to a block of flats or a business must have a process to spot live attacks ready now. It should not be built after the first missed report.
Industrial automation. PLCs, SCADA systems and computer controls for machine tools are listed in Annex III as Industrial Automation & Control Systems (IACS). Here, the practical problem is different from home devices. In a factory, an automatic update can stop a production line. So the law allows exceptions to automatic updates in critical industrial settings. But it does not exempt anyone from the 24-hour reporting duty.
Products already sold. This is the detail that surprises people most. The duty also covers products sold before the law existed, as long as they are still in use and still supported. Take a maker that no longer develops a 2021 camera model, but still supports units installed at active client sites. It must still report an exploited flaw found in that camera. The law does not split products into “new and CRA-compliant” and “old”. It splits them into products still in use and products that have been discontinued.
The practical problem: the platform isn’t ready
Here is the newest and most practical fact in this article. Reports go through ENISA’s Single Reporting Platform (SRP). It is a single online point meant to reach ENISA and the national lead CSIRT at the same time. A few days before the duty took effect, the platform had no published web address and no submission API at launch. And according to ENISA’s own technical guide, its 72-hour counter can show a report as late before 72 hours have really passed since awareness.
For an Italian company, this means one very practical thing. The legal duty exists from day one, but the tool to meet it is still being finished. That is no reason to delay internal preparation. It is a reason not to blindly trust the countdown shown on the platform. Firms should log the exact moment of “awareness” internally, because that is when the legal clock really starts.
The Commission’s 27 July 2026 guidance
On 27 July 2026, the European Commission published non-binding guidance on how to apply the law, as required by Article 26. The document is C(2026) 5252, about 80 pages long. Its most useful part defines “awareness”. The clock does not start when a raw report arrives. It starts when, after a quick first check, there is “a reasonable degree of certainty” that the flaw is really being exploited. This gives a short but real window to check the facts. It is not an excuse to stall, nor an automatic trigger at the first unchecked suspicion.
Italy note
For Italian makers and integrators, the key point is the gap described above. The duty is already in force, while the reporting platform is still being completed. So the safest choice is to set up internal processes now, without waiting for the platform to be finished.
FAQ
What happens if a company misses the 24-hour deadline?
The law sets fines of up to €15 million or 2.5% of yearly global turnover when makers break their duties, including Article 14.
Does this cover vulnerabilities that haven’t been exploited yet?
No. Article 14 only applies to flaws with solid evidence of active use by an attacker, or to severe incidents. A flaw found through good-faith research or a bug bounty, with no sign of attack, does not have to be reported.
Does a product sold in 2022 count?
Yes, if it is still in use and still supported by the maker. The law has no time-based exemption for the duty to report.
Sources
cyberresilienceact.eu, independent Article 14 summary, updated 7 September 2026
Regulation (EU) 2024/2847 of the European Parliament and of the Council, 23 October 2024 (EUR-Lex)
European Commission, application guidance C(2026) 5252, 27 July 2026 (digital-strategy.ec.europa.eu)
ComplexDiscovery, “Cyber Resilience Act reporting starts Sept. 11 on an unfinished platform,” September 2026



