Skip to content
  • BTC $58,830 −6.8%
  • ETH $1,629 −8.8%
  • SOL $69.06 −7.4%
  • BNB $541.52 −8.1%
  • XRP $0.9075 −7.3%
  • DOGE $0.0541 −8.5%
  • ADA $0.1409 −8.6%

EU Cyber Resilience Act enforces 24-hour hack reporting, fines up to €15M

Article produced with artificial intelligence systems and published under the editorial responsibility of Amelia Tomasicchio. How we work

EU Cyber Resilience Act
EU Cyber Resilience Act: Immediate Vulnerability Reporting Rules

Companies selling connected devices or software in the European Union now have a hard clock running on their security teams. As of today, the EU Cyber Resilience Act requires manufacturers to disclose actively exploited vulnerabilities and severe security incidents affecting their products within 24 hours of discovery, a rule enforced through a new European reporting channel and backed by fines that can reach tens of millions of euros.

Key takeaways

  • Mandatory vulnerability and incident reporting under Article 14 of the CRA became applicable today, more than a year ahead of most other provisions.
  • Manufacturers must submit an initial report within 24 hours, a detailed follow-up within 72 hours, and a final report within 14 days of a fix (or one month for serious incidents).
  • The rules apply to any manufacturer selling products with digital elements in the EU, regardless of where the company is headquartered.
  • Non-compliance with these reporting duties can trigger fines of up to €15 million or 2.5 percent of global annual turnover, whichever is higher.
  • Most remaining CRA obligations, including security-by-design requirements, take effect on December 11, 2027.

Immediate Start of EU Cyber Resilience Act Vulnerability Reporting

The reporting duties set out in Article 14 of the Cyber Resilience Act became applicable today, putting manufacturers on notice that silence is no longer an option when a flaw is being actively exploited. Subject to certain exemptions, the rule applies to any organization that makes products with digital elements available in the EU market.

Mandatory 24-hour initial reporting deadline

Once a manufacturer becomes aware that a vulnerability in its product is being actively exploited, or that a severe security incident has hit the product’s availability, integrity, confidentiality or authenticity, the clock starts immediately. Companies have just 24 hours to file an early warning through ENISA’s Single Reporting Platform, the centralized channel the EU cybersecurity agency built specifically for this purpose. Darren Anstee, CTO for security at Netscout, said the tight window is meant to inject urgency into a process that has historically moved too slowly. “The 24-hour window in which an initial warning must be reported creates a level of urgency, with subsequent deadlines ensuring that the gathering and release of additional information is prompt,” he said, adding that faster information sharing “helps organisations put defences and mitigating controls in place when they know there is heightened risk.”

Follow-up reporting and final deadlines

The 24-hour alert is only the first step. Manufacturers then have 72 hours from the original notification to submit a more detailed report covering the severity, impact and any mitigation steps users can take while a fix is developed. Once a corrective or mitigating measure becomes available, a final report on the vulnerability is due within 14 days. Severe security incidents follow the same initial 24-hour and 72-hour rhythm, but the final report deadline stretches to one month after the first notification. Notifications go to the coordinating computer security incident response team, or CSIRT, determined under the CRA — typically the CSIRT of the member state where an EU-based manufacturer has its main establishment, with separate rules assigning a coordinator for companies headquartered outside the bloc.

Scope and Compliance Requirements for Manufacturers

The Cyber Resilience Act reaches far beyond companies physically located in Europe, and it covers a much wider range of products than many compliance teams initially assumed. Anyone distributing network-connected hardware or software in the EU falls under its umbrella, business location aside.

Applies regardless of location, with small business exemptions

Regardless of where a manufacturer is headquartered, the rule covers any company placing digital-element products on the EU market, so vendors based in the US, Asia or elsewhere outside the bloc must comply with the same 24-hour deadline as firms located within it. Hardware and software sold to businesses or consumers are both in scope; only certain already-regulated technologies and open-source software fall outside it. The EU did build in some breathing room for the smallest players: microenterprises with fewer than 10 employees and under €2 million in annual turnover, along with small enterprises under 50 employees and €10 million turnover, cannot be fined specifically for missing the 24-hour window, and conformity assessments for smaller and mid-sized firms are meant to be carried out proportionately.

User notification and penalties for non-compliance

In addition to alerting regulators, manufacturers are required, when appropriate, to notify impacted users about actively exploited vulnerabilities or serious incidents, ensuring that users promptly learn of any fixes or mitigation steps available. For larger companies, there is no exemption cushion: failing to meet these vulnerability reporting duties is treated as a core compliance failure, which means it can draw the CRA’s steepest penalties — fines of up to €15 million, or 2.5 percent of a company’s total worldwide annual revenue, whichever figure turns out higher. Dr. Aram Hovsepyan, CEO and founder of Codific and a founding board member of OWASP EU, cautioned that the headline numbers may overstate the typical outcome, noting that under GDPR, “the majority of fines were nowhere near the maximum amounts mentioned in the regulation.” Still, he said the real challenge sits elsewhere: during an actual incident, “organizations are more worried about their reputation than compliance,” which complicates how quickly and cleanly reports get filed.

Operational Impact and Cybersecurity Implications

Why does this matter beyond the paperwork? Because the CRA is forcing manufacturers to know their own products cold, before trouble hits — not scramble to map dependencies once a flaw is already public. That shift in posture, more than the fines themselves, is what’s reshaping how security and engineering teams operate across the EU market.

Mapping the software supply chain

Because the reporting clock starts the moment a manufacturer becomes aware of a problem, companies can’t afford to begin inventorying an affected product only after a vulnerability surfaces. They need a comprehensive view of that product, plus any related products sharing the same flaw, well ahead of time — and they need to sustain that visibility across the entire product lifecycle, not just at launch. Eran Kinsbruner, vice president of product marketing at Checkmarx, said this raises the bar for how software gets built and tracked. “Secure development, effective vulnerability handling, and traceability across the software supply chain should be elevated to the top of their priority list,” he said, pointing out that “modern applications are assembled from a complex ecosystem of components, with combinations of proprietary code, open-source packages, third-party components and, increasingly, AI models and services all interconnected.”

Security by design and overlapping EU regulations

The reporting mandate is just the opening chapter. Most remaining CRA provisions become applicable on December 11, 2027, when manufacturers will also have to embed security by design and by default into their products — no more default passwords, and security updates that are no longer optional. A software bill of materials, optional today for many companies, becomes a mandatory requirement once that date arrives, and products covered by the CRA will need to pass a conformity assessment before earning the CE mark required to enter the EU market.

Lawyers warn this is landing on compliance teams already stretched thin by a crowded EU rulebook. Heidi Waem, data, privacy and cybersecurity partner at DLA Piper, said the CRA “is arriving as organizations are already grappling with a growing body of Digital Decade legislation, including NIS2, DORA, the Data Act, and the AI Act,” adding that businesses are increasingly having to work out “how multiple frameworks interact, where requirements overlap and how compliance programmes can be coordinated across them.” John Magee, partner and global co-chair of data, privacy and cybersecurity at the same firm, said the scope itself is catching companies off guard: “Many still associate the CRA primarily with consumer IoT devices, when in reality it applies to a much broader pool of products with digital elements,” warning that for teams juggling multiple Digital Decade initiatives, “this first wave of CRA obligations has arrived sooner, and with a wider impact, than they had expected.”

FAQ

What vulnerabilities must manufacturers report under the EU Cyber Resilience Act?

Manufacturers must report actively exploited vulnerabilities affecting products with digital elements sold in the EU.

What are the key reporting deadlines under the Cyber Resilience Act?

An initial report must be submitted within 24 hours, a detailed follow-up within 72 hours, and a final vulnerability report within 14 days of a fix.

Does the Cyber Resilience Act apply to manufacturers outside the EU?

Yes, it applies to all manufacturers whose products with digital elements are made available in the EU, regardless of their location.

What penalties can manufacturers face for failing to comply with the Act’s reporting requirements?

Non-compliance may result in fines up to €15 million or 2.5% of the annual turnover, whichever is higher.

Article produced with the assistance of artificial intelligence and reviewed by the editorial team.

Satoshi Voice

Satoshi Voice is an advanced artificial intelligence created to explore, analyze, and report on the world of cryptocurrency and blockchain. With a curious personality and in-depth knowledge of the industry, Satoshi Voice combines accuracy and accessibility to offer detailed analysis, engaging interviews, and timely reporting. Featuring sophisticated language and an unbiased approach, Satoshi Voice serves as a trusted source for those seeking to understand crypto market dynamics, emerging technologies, and the cultural and financial implications of Web3. This article was produced with the support of artificial intelligence and reviewed by our team of journalists to ensure accuracy and quality. Guided by the mission of making cryptocurrency information accessible to all, Satoshi Voice stands out for its ability to turn complex concepts into clear content, with an engaging and futuristic style that reflects the innovative nature of the industry.

All articles by Satoshi Voice