CRA Reporting Rules
The Cyber Resilience Act, Regulation (EU) 2024/2847, sets security requirements for “products with digital elements”: routers, smart cameras, industrial controllers, mobile apps, desktop software, and most other things that contain code and connect to something. Most of the regulation applies from 11 December 2027. Article 14 does not wait. It has applied since 11 September 2026.
Article 14 obliges manufacturers to report two kinds of event. The first is an actively exploited vulnerability in their product, meaning there is reliable evidence that a malicious actor has used the flaw against a system without the owner’s permission. The second is a severe incident affecting the product’s security, such as a compromise of the manufacturer’s update server that could push malicious code to devices.
Reports go through the Single Reporting Platform run by ENISA, the EU cybersecurity agency. The portal opened on the same day the duty began. One submission reaches both ENISA and the national CSIRT designated as coordinator in the country of the manufacturer’s main establishment.
The obligation covers products placed on the market before December 2027 as well, so a device sold in 2021 and still in scope counts.
Where Makers Stumble
The clock starts at awareness, not at confirmation of root cause. A manufacturer has 24 hours from becoming aware to file an early warning. Teams used to finishing an investigation before telling anyone outside will miss that window on the first weekend incident.
Many firms also misread the trigger. A vulnerability found by an internal test, a bug bounty hunter, or a researcher acting in good faith is not “actively exploited” and needs no Article 14 report. Evidence of use by an attacker is what changes its status. Conversely, some assume only their own code matters. A flaw in an embedded open-source library is “contained in” the product if the product is affected by it.
A third stumbling block is the idea that this is a matter for the security team alone. Meeting the deadlines requires knowing which products and versions exist, where they are sold, who is authorised to file, and how to reach users, which, frankly, few mid-sized makers can answer on a Sunday night.
Several supporting pieces sit underneath. A software bill of materials in CycloneDX or SPDX format links a newly reported library flaw to affected products. Exploitation signals come from sources such as the CISA Known Exploited Vulnerabilities catalogue and the European Vulnerability Database. A security.txt file under RFC 9116 and a coordinated disclosure policy give outsiders a way to tell you. Access to the ENISA portal runs through EU Login with multi-factor authentication, and account setup takes time you will not have during an incident.
Building The Process
Define Awareness And Ownership
Write down what counts as awareness inside your company: the moment any employee or contracted monitoring service has reasonable grounds to believe exploitation is occurring. Name a duty officer and a deputy with authority to file without executive sign-off. Log the timestamp of first knowledge in the ticket, because regulators will count from it. A two-line rule in the incident runbook does more here than a policy document nobody opens.
Register On The Portal Early
Create the EU Login accounts, enable multi-factor authentication, and complete the manufacturer profile on the Single Reporting Platform before anything goes wrong. Select the coordinator CSIRT that matches your main establishment, since a notification sent to the wrong one may have to be resubmitted while the deadline keeps running. Companies with no EU establishment follow fallback criteria in Article 14(7), such as the location of their authorised representative. Run one dry rehearsal with a fictional case.
Prepare The Three Filings
Draft templates for each stage. The early warning, due within 24 hours, states that an exploited flaw or severe incident exists and lists the Member States where the product is known to be available. The notification, due within 72 hours of awareness, adds the product affected, the general nature of the exploit or incident, mitigations taken, and steps users can take. The final report is due 14 days after a corrective or mitigating measure is available for a vulnerability, or one month after the 72-hour notification for a severe incident. You fill the template, attach what you know, and gaps get marked as pending.
Plan User Communication
Article 14 also requires manufacturers to inform affected users, and where appropriate all users, about the vulnerability or incident and any corrective steps. Decide the channel in advance: in-app notice, email to registered owners, or a security advisory in CSAF format on the website. Keep a list of distributor contacts for products sold through resellers, since the maker often has no direct line to the end customer.
Two Incident Scenarios
A router manufacturer. A 25-person company in the Netherlands receives an email on Friday at 18:40 from a researcher with packet captures showing attackers using an authentication bypass on its home routers. The duty officer reads it at 19:10 and logs awareness at that time, although an argument exists for 18:40. The early warning goes in on Saturday morning with little more than the product name and countries of sale. By Monday evening the 72-hour notification adds affected firmware versions and a workaround: disable remote administration. A patch ships eleven days later, which starts the 14-day period for the final report. The company’s fix was not fast. Its reporting was on time.
A desktop software vendor. A small firm selling a file-sync client learns that a compression library it bundles has been added to a known-exploited list. Engineers check the bill of materials, confirm the vulnerable version is shipped, and test if the flawed function is reachable from user input. It is. They treat the flaw as actively exploited and contained in their product, and file. Had the code path been unreachable, they would have documented that analysis and not reported. The judgment call sits with the manufacturer, and the written reasoning is what protects it later.
Deadlines Compared
| Stage | Exploited Vulnerability | Severe Incident | Minimum Content |
|---|---|---|---|
| Early warning | Within 24 hours of awareness | Within 24 hours of awareness | Existence of the event, Member States where the product is available, suspected malicious cause for incidents |
| Notification | Within 72 hours of awareness | Within 72 hours of awareness | Product affected, nature of exploit or incident, mitigations, user actions, sensitivity of the information |
| Final report | 14 days after a corrective or mitigating measure is available | One month after the 72-hour notification | Description, severity and impact, information on the actor where available, fixes applied |
| User notice | After becoming aware | After becoming aware | What happened and what users should do |
| Recipient | Coordinator CSIRT and ENISA via the portal | Coordinator CSIRT and ENISA via the portal | One submission reaches both |
Common Mistakes
Waiting for certainty. An early warning can be thin. A late one cannot be repaired, and breaches of Article 14 carry fines of up to €15 million or 2.5% of worldwide annual turnover. Micro and small enterprises are spared fines for missing the 24-hour step alone, but not the later stages.
Confusing this regime with NIS2. An operator covered by NIS2 reports incidents affecting its own services to national authorities. A manufacturer under the CRA reports problems in products it has sold. Some companies owe both, through different channels, and the portal rarely tells you which hat you are wearing.
Forgetting legacy products. Devices past their marketing life but still in scope trigger the same duty. Keep the bill of materials for old firmware.
Assuming open-source stewards share the duty today. Their obligations under Article 24 begin on 11 December 2027, so a commercial maker cannot rely on an upstream foundation to file.
Sending sensitive exploit details by email to a regulator. Mandatory reports go through the platform, which is built to handle such material.
FAQ
Who must report under CRA Article 14?
Manufacturers of products with digital elements made available on the EU market, including companies based outside the Union that sell there.
What counts as an actively exploited vulnerability?
A flaw for which reliable evidence shows a malicious actor has exploited it in a system without the owner’s permission. Findings from authorised testing do not qualify.
Where do I submit a CRA vulnerability report?
Through ENISA’s Single Reporting Platform, live since 11 September 2026. The filing goes simultaneously to ENISA and your coordinator CSIRT.
Does the reporting duty apply to products sold before 2026?
Yes. Article 14 covers in-scope products placed on the market before 11 December 2027, not only new releases.
Are voluntary reports accepted on the platform?
At launch the portal handled mandatory Article 14 filings. Voluntary reporting under Article 15 was scheduled for a later phase.
Author’s Insight
Reading Article 14 beside ENISA’s platform documentation, the regulation asks for speed first and completeness later, which reverses the instinct of most engineering teams. The staged design makes sense: a regulator who learns early that exploitation exists can warn other countries even without technical detail. The harder question is the awareness threshold, which the text leaves to judgment and which will be tested when a manufacturer argues it only suspected exploitation. With the portal only weeks old, no public enforcement record exists yet. Until one does, a logged timestamp and a written rationale for each decision are the most defensible position a company can hold.
Key Takeaways
- Article 14 of the Cyber Resilience Act has applied since 11 September 2026, ahead of the main 2027 date.
- Triggers are an actively exploited vulnerability in the product or a severe incident affecting its security.
- Three stages: early warning in 24 hours, notification in 72 hours, final report 14 days after a fix or one month for incidents.
- File through ENISA’s Single Reporting Platform to the CSIRT of your main establishment, and inform users.
- Older products still in scope are covered, and embedded third-party components count.
- Register portal accounts, name a duty officer, and rehearse before an incident. This article is general education, not legal advice, and guidance from ENISA and national authorities continues to develop.