The Question
"We manufacture connected devices and the software that runs on them, sold across the EU. Our product-security team has been told that Cyber Resilience Act reporting 'went live' in September, but the full CRA does not apply until December 2027. What exactly do we have to report today, to whom, and how fast — and what is still not settled?"
The Short Answer
Article 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847) has applied since 11 September 2026, more than a year ahead of the rest of the Regulation. It covers two things: actively exploited vulnerabilities in your products and severe incidents affecting the security of your products. Each must be reported through ENISA's Single Reporting Platform, via the endpoint of the CSIRT designated as coordinator in the member state of your main establishment, with the notification made available to ENISA at the same time. The clock is a 24-hour early warning, a 72-hour notification, and a final report (14 days after a fix is available for a vulnerability; one month after the 72-hour notification for an incident). It applies to products already on the market, not only to new ones. The platform is operational, and the delegated act on delaying dissemination is in force. Still moving: the platform itself (web-only, English-only, no API yet), and an optional implementing act on notification format that has not appeared.
The Detail
Why reporting applies before the rest of the CRA
Article 71(2) sets the general application date at 11 December 2027 but carves out Article 14, which applies from 11 September 2026. Article 69(3) adds that Article 14 also covers in-scope products placed on the market before 11 December 2027. In practice, your installed base is already in scope for reporting, even though under Article 69(2) the rest of the Regulation reaches products placed on the market before 11 December 2027 only if they are substantially modified from that date.
ENISA's platform FAQ, citing subsections 5.1 and 5.3 of the Commission's CRA implementation FAQ, adds a useful timing clarification: there is no retrospective reporting where the manufacturer already knew of the exploitation before 11 September 2026, but if you first became aware of exploitation on or after that date, the obligation applies even if the vulnerability itself was known earlier.
Trigger one: an actively exploited vulnerability
The CRA defines an actively exploited vulnerability (Article 3(42)) as one where there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. A vulnerability that is merely critical, or for which a public proof of concept exists, does not by that fact alone meet the test. The trigger is evidence of exploitation.
For each such vulnerability, Article 14(2) requires:
| Stage | Deadline | Minimum content |
|---|---|---|
| Early warning | Without undue delay, at most 24 hours after becoming aware | Where applicable, the member states in which you know the product has been made available |
| Vulnerability notification | Without undue delay, at most 72 hours after becoming aware | General information on the product, the nature of the exploit and vulnerability, corrective or mitigating measures taken and those users can take, and how sensitive you consider the information |
| Final report | No later than 14 days after a corrective or mitigating measure is available | Description, severity and impact; information on the malicious actor where available; details of the security update or other corrective measures |
Trigger two: a severe incident affecting product security
Article 14(5) treats an incident as severe where it affects, or could affect, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or where it has led, or could lead, to malicious code being introduced or executed in the product or in a user's network and information systems. A compromised build pipeline or a hijacked update channel are the obvious examples of the second limb.
Article 14(4) sets the same staged rhythm with different content:
| Stage | Deadline | Minimum content |
|---|---|---|
| Early warning | At most 24 hours after becoming aware | At least whether the incident is suspected to be caused by unlawful or malicious acts; member states where the product is available |
| Incident notification | At most 72 hours after becoming aware | Nature of the incident, an initial assessment, measures taken and measures users can take, and how sensitive you consider the information |
| Final report | Within one month after the 72-hour notification | Detailed description, severity and impact; likely threat type or root cause; applied and ongoing mitigation |
In both cases, the coordinating CSIRT may ask for an intermediate status report (Article 14(6)).
To whom: one submission, routed by main establishment
You do not report separately to each country. Article 14(7) requires submission through the Single Reporting Platform using the endpoint of the CSIRT designated as coordinator in the member state of your main establishment, with the notification simultaneously accessible to ENISA. Main establishment means where cybersecurity decisions about your products are predominantly taken; failing that, the member state of your establishment with the highest number of employees in the EU. Manufacturers with no EU establishment follow a fallback order: the member state of the authorised representative, then importer, then distributor (each judged by the highest number of your products), then where the most users are located.
That CSIRT then disseminates the notification to the CSIRTs of the member states where you said the product is available (Article 16(2)) and passes the relevant information to national market surveillance authorities (Article 16(3)). ENISA's FAQ notes that choosing the wrong coordinating CSIRT can lead to the notification being invalidated and resubmitted, so settle the main-establishment question in advance, not during an incident.
Users must be told too
Reporting to authorities is not the whole obligation. Article 14(8) requires you to inform impacted users, and where appropriate all users, of the vulnerability or incident and of any mitigation they can apply, where appropriate in a structured, machine-readable format. If you do not inform them in time, the coordinating CSIRTs may do so themselves.
What is settled now
- The platform is live. ENISA deployed the initial operating capability of the Single Reporting Platform on 11 September 2026, and the Commission's CRA reporting page lists it as operational from that date. ENISA reports an upgrade to version 1.3 on 4 November 2026, with documentation still being updated.
- The delegated act on delaying dissemination is in force. Commission Delegated Regulation (EU) 2026/881, adopted 11 December 2025 under Article 14(9) and published in the Official Journal on 20 April 2026, sets the conditions under which the receiving CSIRT may hold back onward dissemination. One condition is that you have told the CSIRT an effective mitigation is expected within 72 hours; if it does not arrive in that window, the notification goes out. The CSIRT decides — you can request a delay and flag sensitivity, but you cannot impose one.
- Non-binding guidance exists. The Commission published its first set of CRA implementation guidance on 27 July 2026, covering, among other topics, reporting obligations. Its CRA implementation FAQ addresses reporting in Section 5.
What is still unsettled
- Platform maturity. At launch the platform accepts only mandatory notifications through a web interface: ENISA's FAQ states there is no API at initial release, the interface is in English only, and voluntary reporting under Article 15 is deferred to a later phase. Access requires an EU Login account with multi-factor authentication; ENISA allows one primary and up to 20 secondary representatives per manufacturer, and verification by the CSIRT runs in parallel with reporting rather than blocking it (an unverified representative can submit up to 20 notifications before verification becomes mandatory). The FAQ also warns that the platform's 72-hour counter is currently set 48 hours after the early warning and that counters do not replace the legal deadlines. Track the deadlines from your own awareness timestamp.
- Notification format. Article 14(10) allows, but does not require, the Commission to specify format and procedures by implementing act. As of 17 November 2026 we found no such act listed on the Commission's CRA implementation or reporting pages. Until one appears, the platform's own fields and ENISA's glossary are the de facto format.
- Open-source software stewards. Their reporting duty under Article 24(3) applies only from 11 December 2027.
- Cross-regime reporting. The Digital Omnibus proposal (COM(2025) 837) includes a single entry point for incident reporting across EU instruments. It remains in the legislative process: the Council adopted its negotiating mandate on 21 October 2026, favouring national entry points plus an EU-level information point. Nothing in it changes your Article 14 duties today.
What to do this quarter
First, make "actively exploited" an explicit triage outcome. Your PSIRT process should record when reliable evidence of exploitation first reached the organisation. That timestamp starts the 24-hour clock, and it is the fact a regulator will ask about first.
Second, prepare registration before you need it. Determine your main establishment and coordinating CSIRT now, and decide who your primary representative is. ENISA advises registering on the platform only when a notification is needed, but EU Login accounts with multi-factor authentication can be created in advance, so have those accounts and the internal decision ready before an incident.
Third, plan for manual submission. With no API, notifications are entered by hand. Keep a pre-filled draft structure per product line so the 24-hour early warning is a matter of minutes, not hours.
Fourth, align with NIS2 where both apply. If you are also an essential or important entity under NIS2, a single event can trigger both CRA product reporting and NIS2 entity reporting. They are separate obligations with different recipients; map both into the same incident runbook.
Note that Article 64(10) exempts microenterprises and small enterprises from administrative fines for missing the 24-hour early-warning deadline. The obligation itself still applies to them.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act) — Articles 3(42), 14, 15, 16, 24(3), 64(10), 69(2)–(3), 71(2)
- Commission Delegated Regulation (EU) 2026/881 — conditions for delaying dissemination of notifications (adopted 11 December 2025; OJ 20 April 2026)
- European Commission — Cyber Resilience Act: reporting obligations
- European Commission — CRA implementation and Commission guidance of 27 July 2026
- ENISA — The CRA Single Reporting Platform is launched (11 September 2026)
- ENISA — Single Reporting Platform and SRP FAQ
- European Parliament Legislative Train — Digital package (status of COM(2025) 837)
- Companion pieces: The CRA SBOM Mandate and Compliance Q&A Ed.004 on NIS2 reporting templates