New obligation to report vulnerabilities and incidents from 11 September 2026

Huub de Jong Tom de Wit

On 11 September 2026, an important part of the Cyber Resilience Act (CRA) will become applicable. From that date, Article 14 of the CRA will apply, requiring manufacturers of products with digital elements to report certain vulnerabilities and security incidents.

Which products are subject to the reporting obligation?

The new reporting obligation will, in principle, apply to manufacturers of products with digital elements that are placed on the market in the European Union. These include hardware, such as smart devices (IoT), as well as software, such as mobile applications.

The obligation is not limited to new products: it may also be relevant to products that are already on the market. Vulnerabilities that were already known before 11 September 2026, however, do not have to be reported.

Certain categories of products are excluded from the scope of the CRA and, consequently, from this reporting obligation, including where they are already subject to specific EU legislation. This applies, for example, to medical devices.

What must be reported?

From 11 September 2026, manufacturers must report:

  • actively exploited vulnerabilities affecting a product with digital elements; and
  • severe incidents having an impact on the security of a product with digital elements.

For actively exploited vulnerabilities, it is irrelevant whether a patch has already been made available. A vulnerability for which a security update has already been released may therefore still be subject to the reporting obligation.

24 hours, 72 hours and a final report

Similar to the phased reporting mechanism under NIS2 (implemented in the Netherlands through the Cyberbeveiligingswet), the CRA provides for several reporting stages. In principle, an early warning must be submitted within 24 hours, followed by a more detailed notification within 72 hours. A final report must subsequently be submitted.

The 24-hour period starts to run as soon as the manufacturer becomes aware of the actively exploited vulnerability or severe incident. In this respect, the CRA follows an approach also found in other EU reporting regimes: the reporting period starts when the organisation has sufficient knowledge of the relevant incident or vulnerability.

Notifications are submitted through the designated reporting infrastructure, in which ENISA plays a central role. In practical terms, manufacturers in the Netherlands will submit their notifications through their MijnNCSC account.

Not every vulnerability has to be reported

The reporting obligation does not mean that every newly discovered vulnerability must automatically be reported to the authorities.

A zero-day vulnerability discovered, for example, during internal research or product testing does not have to be reported as an actively exploited vulnerability under Article 14 CRA as long as there are no indications that the vulnerability has actually been exploited.

The CRA does, however, provide for the possibility of voluntarily reporting certain vulnerabilities.

Users must also be informed

The similarities with other European reporting regimes extend beyond the short reporting deadlines. As with the obligation to notify personal data breaches under the GDPR and the obligations relating to security incidents under NIS2, the CRA may also require others to be informed of an incident or vulnerability.

In certain circumstances, manufacturers must inform affected users of a product with digital elements about an incident or actively exploited vulnerability and, where necessary, about measures that users can take to mitigate its consequences.

This means that, in the event of a cybersecurity incident, a manufacturer must assess not only whether and when a notification must be made, but also which users must be informed and what information they need.

Do not wait until December 2027

Most of the CRA’s obligations will become applicable from 11 December 2027. These include important requirements relating to vulnerability handling. Among other things, manufacturers will be required to have a policy in place for the coordinated disclosure of vulnerabilities.

It would, however, be unwise to wait until December 2027 before putting such processes in place. After all, the reporting obligation under Article 14 will already apply from 11 September 2026.

Moreover, this reporting obligation does not exist in isolation. A single cybersecurity incident may trigger several, partly overlapping obligations under, for example, the CRA, NIS2/Cybersecurity Act, GDPR and AI Act. Different reporting thresholds, deadlines, competent authorities and information obligations may apply.

For manufacturers of products with digital elements, now is therefore the time not only to establish a CRA reporting procedure, but above all to implement an integrated vulnerability and incident response process. This will enable them to determine quickly when an incident occurs, which reporting obligations have been triggered, which deadlines apply, which authorities must be notified and what communications to users are required.