Update (2 October 2026): the CRA Single Reporting Platform is now operational.
The manufacturer reporting obligations under Article 14 of the Cyber Resilience Act have applied since September 11, 2026.
Reporting Process
Manufacturers must report actively exploited vulnerabilities and severe incidents affecting the security of products already on the EU market.
Definitions
- Actively exploited vulnerability
- A flaw that has been reliably proven to be exploited by a malicious actor without the system owner’s permission.
- Severe incident
- An incident that negatively affects—or could negatively affect—the product’s ability to protect the availability, authenticity, integrity, or confidentiality of sensitive or important data or functions. An incident is also severe if it has led—or could lead—to the introduction or execution of malicious code in the product or in a user’s network and information systems.
Reporting Deadlines
For both actively exploited vulnerabilities and severe incidents, manufacturers must submit:
- Early warning: Without undue delay and no later than 24 hours after becoming aware of the vulnerability or incident.
- Vulnerability or incident notification: Without undue delay and no later than 72 hours after becoming aware of it, providing the information available at that stage, including any corrective or mitigating measures.
The final-report deadline depends on what is being reported:
- Actively exploited vulnerability: No later than 14 days after a corrective or mitigating measure is available—not after users have implemented it.
- Severe incident: Within one month after submitting the incident notification described above.
The 72-hour notification and final report are required unless the relevant information has already been provided. The coordinating CSIRT may also request an intermediate status report.
Submission Platform
- Reports are submitted via the CRA Single Reporting Platform, developed by ENISA
- Operational since September 11, 2026
Distribution
- Manufacturers notify the CSIRT designated as coordinator and ENISA simultaneously through the platform.
- Manufacturers with a main establishment in the EU use the endpoint of the coordinating CSIRT in that Member State. Article 14(7) sets out the selection rules for manufacturers without a main establishment in the EU.
- The coordinating CSIRT handles onward sharing with other relevant coordinating CSIRTs under Article 16, including the rules on delaying dissemination of sensitive notifications.
Preparing for Reporting Obligations
Manufacturers should:
Establish Monitoring and Reporting Capabilities
- Implement systems and processes to continuously monitor for product vulnerabilities and product related security incidents.
- Ensure the team responsible for cybersecurity can quickly detect, document, and escalate relevant events.
Impact Assessment and Risk Mitigation
- Be able to assess the impact of any detected vulnerability or incident on the product and its users.
- Implement procedures to mitigate risks promptly, including patches, updates, or other corrective measures.
Prepare Reporting Procedures
- Set up processes to submit reports through the CRA Single Reporting Platform, operational since September 11, 2026.
- Build the reporting deadlines into your response procedures: early warning within 24 hours and notification within 72 hours of awareness, both without undue delay.
- Track the final-report trigger separately: availability of a corrective or mitigating measure for vulnerabilities; submission of the incident notification for severe incidents.
Train Teams and Assign Responsibilities
- Assign a dedicated team or individual responsible for compliance with CRA reporting requirements.
- Train staff on recognizing vulnerabilities, assessing severity, and following reporting protocols.
Document Everything
- Maintain detailed records of detected vulnerabilities, incidents, assessments, and mitigation measures.
- Documentation will help demonstrate compliance if audited by regulators.