TL;DR: For a qualifying actively exploited vulnerability or severe security incident, manufacturers must notify the relevant EU country's CSIRT and ENISA. The CSIRT forwards the report to other EU CSIRTs and CRA regulators. Notices to other regulators and information-sharing bodies are considerations, while user and component-maintainer notices apply under their stated conditions.

  • Manufacturers must notify the relevant EU country's CSIRT and ENISA about the specified reporting triggers.
  • The relevant CSIRT forwards the report to other EU CSIRTs and CRA regulators.
  • Notices to other regulators, jurisdictions or information-sharing groups are considerations, not automatic CRA requirements.
  • Notify users when a qualifying event affects them, and notify a component maintainer when a product vulnerability relates to that third-party component.

After a qualifying CRA report, manufacturers must distinguish the notices required by the Cyber Resilience Act from other disclosures to consider. CRA vulnerability reporting requires manufacturers to notify the relevant EU country’s CSIRT and ENISA when a covered product contains an actively exploited vulnerability or suffers a severe security incident. The CSIRT then forwards the report to other EU CSIRTs and CRA regulators. Other regulators and information-sharing groups are possible additional recipients, not automatic CRA destinations.

For a qualifying actively exploited vulnerability or severe security incident, manufacturers must notify the relevant EU country’s CSIRT and ENISA. The CSIRT forwards the report to other EU CSIRTs and CRA regulators. Notices to other regulators and information-sharing bodies are considerations, while user and component-maintainer notices apply under their stated conditions.

That distinction matters when you are deciding how to handle a vulnerability or incident. Product scope, the manufacturer’s identity, user impact and any third-party component issue all affect who may need information – and why.

What does CRA vulnerability reporting change?

CRA vulnerability reporting adds hard legal reporting obligations to a field where vulnerability disclosure had mainly been shaped by voluntary information-sharing efforts. The source states that the CRA’s first part, including reporting obligations, will come into force on 11 September 2026. Skadden’s CRA reporting FAQ identifies that date and the new reporting duties.

The remaining CRA obligations, including cybersecurity conformity assessments for new products, are stated to apply from 11 December 2027. Skadden describes the reporting obligations as applying to manufacturers of connected software and hardware products. These dates are presented as stated in the source, not as independent legal advice.

The disclosure question does not end with the first filing. A report may raise separate questions about other regulators, information-sharing bodies, affected users and component maintainers. The legal basis and conditions differ for each recipient.

Which products and manufacturers are covered?

The reporting duties apply to manufacturers of products with digital elements made available in the EU, regardless of when those products were first released. Covered examples include connected software and hardware such as mobile apps and IoT devices, including products made available for free. Back-end or cloud services are also in scope when they are necessary for those products to perform their functions.

Identifying the boundaries of a product and its supporting systems can be complex. So can identifying the CRA-regulated manufacturer in supply chains involving intragroup arrangements or white-labelling. A product’s commercial label or internal organisational structure may not, by itself, resolve who holds the manufacturer role.

What should you map before a reportable event?

Use a focused mapping checklist:

  • Identify products with digital elements made available in the EU.
  • Identify the back-end or cloud services necessary for those products to function.
  • Determine which entity is the manufacturer for each product, including in intragroup or white-labelling arrangements.
    This is not a detailed technical inventory exercise. It is a way to clarify which products, supporting services and responsible entities may be relevant when a qualifying event occurs.

Which events trigger a CRA report?

The stated government-reporting triggers are an actively exploited vulnerability contained in a product with digital elements, or a severe incident affecting that product’s security. For either trigger, the manufacturer must notify the relevant EU country’s CSIRT and ENISA. The source does not say that every vulnerability or security incident is reportable.

A taut folded-paper barrier buckles along a narrow, rainbow-edged seam.
A taut folded-paper barrier buckles along a narrow, rainbow-edged seam.

A severe incident is one that negatively affects the product’s ability to protect important data or functions, or leads to malicious code being introduced or executed. These are the source’s descriptions of the relevant trigger; they should not be broadened to cover incidents that do not meet the stated conditions.

Who receives a CRA report – and who else might learn about it?

For a qualifying event, the manufacturer must notify the relevant EU country’s CSIRT and ENISA. The relevant CSIRT forwards the notification to other EU countries’ CSIRTs and CRA regulators. This onward distribution is part of the stated reporting route; it is not the same as a manufacturer separately notifying every possible recipient.

Regulator notifications are usually not public. The source also notes that CSIRTs may notify affected users in specified circumstances. That is distinct from the manufacturer’s own duty to notify users when a qualifying vulnerability or incident affects them.

Manufacturers should consider whether a CRA report should also prompt notice to other regulators, including GDPR or NIS2 authorities, or to authorities in other jurisdictions. Sectoral information-sharing and analysis centers are another possible recipient group to consider. These are disclosure questions, not automatic CRA notification requirements. The source does not say that every CRA report must be repeated to these recipients.

The same event may also require attention to vulnerability handling and remediation prioritization. The source connects reporting with the possibility of increased pressure to address an actively exploited vulnerability; it does not make fixing the vulnerability part of the reporting duty itself. Keep that distinction clear when considering what to share and how the issue is being handled.

When must users and component maintainers be notified?

When an actively exploited vulnerability or severe incident affects product users, the manufacturer must notify those users and explain steps they can take to mitigate risk. Examples include updating configurations or patching systems. The condition matters: the source does not say that every report to regulators automatically requires a customer notice.

A folded paper canopy shelters delicate layered forms beside a bright patch of paper.
A folded paper canopy shelters delicate layered forms beside a bright patch of paper.

A separate notification applies when a vulnerability in the product relates to a third-party component. The manufacturer must inform the component maintainer and share any patch that addresses the vulnerability. These duties concern different recipients and circumstances from the initial government report.

For product leaders, the practical task is to keep these distinctions visible: required authority notices, possible further disclosures, user notices when users are affected, and component-maintainer notification when a third-party component is involved. Connecting those decisions to vulnerability handling and incident response is relevant; adding an unsupported disclosure process is not.

Frequently asked questions

Does a CRA report automatically require notifying GDPR or NIS2 authorities?

No. The source presents notices to GDPR or NIS2 authorities as matters for manufacturers to consider, not as automatic CRA reporting requirements. The mandatory CRA notices described here are to the relevant EU country’s CSIRT and ENISA, followed by onward distribution from that CSIRT.

When must a manufacturer notify product users?

A manufacturer must notify users when an actively exploited vulnerability or severe incident affects them. The notice must explain steps users can take to mitigate risk, such as updating configurations or patching systems.

What if the vulnerability relates to a third-party component?

The manufacturer must inform the component maintainer and share any patch addressing the vulnerability. This is a distinct notification from the required report to the CSIRT and ENISA.

Key takeaways

  • Manufacturers must notify the relevant EU country’s CSIRT and ENISA about the specified reporting triggers.
  • The relevant CSIRT forwards the report to other EU CSIRTs and CRA regulators.
  • Notices to other regulators, jurisdictions or information-sharing groups are considerations, not automatic CRA requirements.
  • Notify users when a qualifying event affects them, and notify a component maintainer when a product vulnerability relates to that third-party component.

Practical tips

  • Map covered products and the back-end or cloud services necessary for them to function.
  • Identify the entity responsible as manufacturer, including in intragroup and white-labelling arrangements.
  • Keep required authority notifications distinct from possible further disclosures and conditional notices to users or component maintainers.



Related Posts

Contact

Slovak Republic+421911948347

DATATIP, s.r.o.
Alžbetina 30
Košice 040 01
Company ID: 36869112
VAT ID: SK2023131594
IBAN: SK80 8330 0000 0022 0024 5482

Czech Republic+420773926377

DATATIP CZ, s.r.o.
Pelušková 1443
Praha 198 00
Company ID: 24853577
VAT ID: CZ24853577
IBAN: CZ81 2010 0000 0023 0033 8790

Privacy Preference Center