← Back to blog

The Cyber Resilience Act's Vulnerability Reporting Rules Are Live

The EU Cyber Resilience Act's vulnerability and severe-incident reporting duties began in September 2026. Product teams should map scope, evidence, and response ownership now.

The EU Cyber Resilience Act (CRA) is no longer only a 2027 planning item: its vulnerability and severe-incident reporting obligations began applying on 11 September 2026. Developers building software products for the EU market need to know whether the rules apply to their product and how an incident will reach the people responsible for reporting it.

The CRA applies to manufacturers of products with digital elements, a category that includes software products. It does not automatically make every website or hosted service a regulated product. The European Commission's July 2026 guidance clarifies difficult boundaries, including when a remote data processing solution is part of a product. Teams should document the product, manufacturer, and service relationship instead of assuming that “SaaS” settles the question.

What Must Be Reported

The reporting duty covers two distinct situations: an actively exploited vulnerability in a product with digital elements, and a severe incident that impacts the security of such a product. These are product-security reports. They are not a substitute for assessing separate duties under data-protection, network-security, customer-contract, or sector-specific rules.

For an in-scope manufacturer, the CRA sets staged deadlines after it becomes aware of a reportable event. An early warning is due within 24 hours; a more complete notification follows within 72 hours. A final report on an actively exploited vulnerability is due within 14 days after a corrective or mitigating measure is available. For a severe incident, the final report is due within one month after the incident notification. The Regulation routes these reports through the single reporting platform to the relevant CSIRT coordinator and ENISA.

The clock is a reason to prepare an intake and escalation process before an incident, not to wait until every technical detail is known. Assign an owner who can start the reporting workflow, preserve timestamps, and coordinate security, product, legal, and communications staff.

Build the Reporting Path Into Operations

Start with an inventory of products, versions, components, and responsible manufacturers. Link that inventory to vulnerability intake, release management, and incident response. If a cloud service or third-party component is part of a product, record who can establish whether a flaw affects the product's security and who can ship a mitigation.

Define a minimum incident record: when the team became aware, affected product and versions, what is known about exploitation or impact, current mitigations, and a contact who can answer follow-up questions. Separate confirmed facts from hypotheses, and update the record as evidence changes. Do not copy entire customer requests, analytics payloads, or unrelated personal data into a security case merely because they might be useful later.

Test the process with a tabletop exercise. Simulate an actively exploited dependency and verify that the on-call engineer can identify the manufacturer, start the 24-hour escalation, find the current product inventory, and reach the person authorized to submit a report. A policy document is not a reporting system if nobody can execute it under time pressure.

Keep the CRA and Privacy Workflows Distinct

The CRA's reporting obligation and a personal-data breach assessment answer different questions. A security incident can trigger product reporting without involving personal data; a personal-data breach can require a separate GDPR assessment even when the CRA does not apply. Keep the evidence coordinated but do not assume one notification satisfies another law's recipient, threshold, or deadline.

The Commission's 2026 guidance is non-binding, but it gives practical examples for scope and reporting. The CRA's main product obligations apply from 11 December 2027; reporting began earlier. A product inventory, named decision owners, and a rehearsed escalation path are the useful work to do now.

Sources

Comments

Loading comments…