Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform. The CRA's main requirements follow on 11 December 2027.

Key takeaways
- CRA reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026, including for products placed on the market before that date.
- Deadlines are 24 hours for an early warning, 72 hours for a notification, and 14 days or one month for the final report, filed once through ENISA's Single Reporting Platform.
- Full application on 11 December 2027 requires secure-by-design products, a defined support period of normally at least five years, an SBOM, a vulnerability handling process and CE marking.
The Cyber Resilience Act (Regulation (EU) 2024/2847, CRA) sets horizontal cybersecurity requirements for hardware and software products sold in the EU [1]. It entered into force on 10 December 2024 and applies in stages. The first operational obligation, mandatory reporting of actively exploited vulnerabilities and severe incidents, started on 11 September 2026 [3]. The bulk of the regulation applies from 11 December 2027 [2]. This article covers the timeline, scope and what manufacturers and software vendors should have in place now.
The timeline
| Date | Milestone |
|---|---|
| 10 December 2024 | CRA enters into force [2] |
| 11 June 2026 | Rules on notification of conformity assessment bodies (Chapter IV) apply [2] |
| 11 September 2026 | Manufacturer reporting obligations (Article 14) apply [3] |
| 11 December 2027 | Main obligations apply, including essential requirements, conformity assessment and CE marking; open-source steward reporting applies [2][4] |
Two points are worth stressing. First, reporting applies to all products with digital elements made available on the EU market, including those placed on the market before December 2027 [2][5]. Second, according to the Commission’s guidance, manufacturers do not need to report retrospectively exploitation they knew about before 11 September 2026 [5].
If you cannot tell within hours which of your products contain a vulnerable component, the 24-hour clock will beat you.
Who is in scope
Products with digital elements
The CRA covers hardware and software products, and their remote data processing solutions, made available on the EU market in the course of a commercial activity, where the intended or reasonably foreseeable use includes a direct or indirect data connection to a device or network [2]. This includes consumer IoT, industrial components, operating systems, desktop and mobile applications, firmware and software components sold separately.
What is generally out of scope
- Pure SaaS: the Commission’s guidance, published on 27 July 2026, indicates that software run remotely for user access generally falls outside the CRA, unless it is a remote data processing solution without which a product could not perform one of its functions [6].
- Products covered by specific legislation, such as medical devices, certain vehicles and aviation equipment [1].
- Free and open-source software that is not made available in the course of a commercial activity. Legal persons that systematically support open-source projects intended for commercial use (“open-source software stewards”) have lighter obligations [2][6].
Product classes
Most products fall into the default category and can be self-assessed. “Important” products (Annex III, class I and II) and “critical” products (Annex IV) face stricter conformity assessment, with technical descriptions set out in Implementing Regulation (EU) 2025/2392 [2]. For class I, self-assessment is possible only when harmonised standards, common specifications or a certification scheme are applied [2].
Roles
Obligations fall mainly on manufacturers, but importers and distributors have their own verification duties [2]. Anyone who substantially modifies a product becomes its manufacturer for CRA purposes [6].
Reporting: what applies since 11 September 2026
What must be reported
Manufacturers must notify actively exploited vulnerabilities in their products and severe incidents having an impact on the security of their products [1][3].
Deadlines
- Early warning: within 24 hours of becoming aware.
- Notification: within 72 hours of becoming aware.
- Final report: for an actively exploited vulnerability, no later than 14 days after a corrective or mitigating measure is available; for a severe incident, within one month of the notification [3].
How
Reports are submitted once through ENISA’s Single Reporting Platform, which launched on 11 September 2026 [4]. The notification goes to the CSIRT designated as coordinator in the Member State of the manufacturer’s main establishment and, simultaneously, to ENISA [3]. Manufacturers must also inform impacted users, and where appropriate all users, about the vulnerability or incident and any mitigations [5].
Microenterprises and small enterprises cannot be fined for missing the 24-hour early warning deadline [2]. Penalties for other infringements are set nationally within the CRA’s maximum amounts [1].
What full application in December 2027 requires
From 11 December 2027, products placed on the EU market must meet the essential requirements in Annex I [1]. In summary:
- Security by design and default: products delivered without known exploitable vulnerabilities, with a secure default configuration, access control, data protection and a minimised attack surface.
- Vulnerability handling: a coordinated vulnerability disclosure policy, security updates provided free of charge where possible separately from feature updates, and regular testing.
- Software bill of materials: identification and documentation of components, including an SBOM in a commonly used, machine-readable format covering at least top-level dependencies.
- Support period: normally at least five years, unless the product is expected to be in use for less time, with the end date clearly stated at the time of purchase [6].
- Documentation and conformity: technical documentation, an EU declaration of conformity and CE marking [2].
Maximum fines for breaching the essential requirements or the obligations in Articles 13 and 14 are EUR 15 million or 2.5% of worldwide annual turnover, whichever is higher [1].
Status of standards and notified bodies (October 2026)
Two dependencies remain incomplete:
- Harmonised standards: as of September 2026, no CRA harmonised standard had been cited in the Official Journal, and a draft amendment to the standardisation request would push delivery of horizontal and vulnerability-handling drafts to 31 October 2026 and product-specific drafts to 31 December 2026 [8]. These are delivery dates for drafts, not citation dates.
- Notified bodies: although Chapter IV has applied since 11 June 2026, no CRA notified body had been designated in the Commission’s NANDO database as of September 2026 [7].
These points come from an independent tracker and may have changed; check the Commission’s standardisation page and NANDO before planning conformity assessment. Manufacturers of important class II or critical products, which need third-party assessment, should watch this closely [2].
What to have in place now
- Product inventory and classification: list every product and version on the EU market, map each to a CRA class, and identify the legal manufacturer and coordinating CSIRT.
- Reporting runbook: define what “becoming aware” means internally, who decides, and who files. Set up access to the Single Reporting Platform in advance and prepare templates for each stage [5].
- Component visibility: generate SBOMs in your build pipeline so you can answer within hours whether a newly exploited vulnerability affects you.
- Vulnerability disclosure policy: publish a contact point and coordinated disclosure policy now; it supports reporting today and is required from 2027.
- Supplier and open-source due diligence: the CRA requires due diligence on third-party components, including open source [6].
- Support period decisions: agree support periods per product line and the commercial model to deliver free security updates.
- Gap assessment against Annex I: start with high-volume and likely important-class products, and plan conformity assessment capacity early.
Closing note
Secrato helps organisations manage frameworks such as NIS2, DORA and ISO/IEC 27001 in one EU-hosted platform, with shared controls, evidence and audit trails.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: https://eur-lex.europa.eu/eli/reg/2024/2847/oj
- European Commission, “The Cyber Resilience Act – Summary of the legislative text”: https://digital-strategy.ec.europa.eu/en/policies/cra-summary
- European Commission, “Cyber Resilience Act – Reporting obligations”: https://digital-strategy.ec.europa.eu/en/policies/cra-reporting
- ENISA, “The CRA Single Reporting Platform is launched”, 11 September 2026: https://www.enisa.europa.eu/news/the-cra-single-reporting-platform-is-launched
- Hogan Lovells, “EU Cyber Resilience Act: Vulnerability and incident reporting obligations now apply and ENISA’s Single Reporting Platform is live”, 11 September 2026: https://www.hlc.com/en/publications/eu-cyber-resilience-act-vulnerability-and-incident-reporting-obligations-now-apply
- Orrick, “EU Cyber Resilience Act: New Guidance Clarifies Scope, Reporting and Product Requirements for Manufacturers”, 8 September 2026: https://www.orrick.com/en/Insights/2026/09/EU-Cyber-Resilience-Act-New-Guidance-Clarifies-Scope-Reporting
- CyberResilienceAct.eu (independent), “On 11 June 2026, the CRA’s rules on notified bodies started to apply”, updated September 2026: https://www.cyberresilienceact.eu/news/cra-notified-bodies-rules-apply-11-june-2026.html
- CyberResilienceAct.eu (independent), “CRA standardisation deadlines pushed back two months”, updated September 2026: https://www.cyberresilienceact.eu/news/cra-standardisation-deadlines-pushed-back-two-months.html