CRA Reporting Obligations: What Begins 2026 vs 2027

The Cyber Resilience Act reporting obligations arrive in two stages. Under the EU Cyber Resilience Act (Regulation (EU) 2024/2847), Article 14 reporting starts 11 September 2026 — reactive notification of actively exploited vulnerabilities and severe incidents only. The full lifecycle duties (Article 13, Annex I) follow on 11 December 2027. Knowing the difference is your roadmap.

TL;DR

  • From 11 September 2026 the CRA reporting duties are reactive only: actively exploited vulnerabilities and severe incidents.
  • Full lifecycle obligations follow on 11 December 2027 — two horizons that need two different capabilities.

With the EU Cyber Resilience Act in its staged application period, manufacturers face a dual horizon. The Cyber Resilience Act reporting obligations under Article 14 begin on 11 September 2026; full applicability follows on 11 December 2027. This builds on our EU Cyber Resilience Act overview, the CRA guidance, and CRA vulnerability reporting — here we set them in context.

What the Cyber Resilience Act reporting obligations require from 11 September 2026

The first stage focuses exclusively on notifying actively exploited vulnerabilities and severe incidents. From September 2026, manufacturers must inform ENISA and the designated CSIRT coordinator via the Single Reporting Platform, and inform their users, whenever they become aware that a vulnerability is being actively exploited or that a severe incident has compromised their product’s security. Reporting then proceeds in three steps: an early warning within 24 hours, a notification within 72 hours, and a final report within 14 days after mitigation is available — or, for severe incidents, within one month of the detailed report. Users must be informed promptly and in machine-readable form, and CSIRTs may notify users directly if the manufacturer fails to.

Cyber Resilience Act reporting obligations chain under the EU Cyber Resilience Act: 24h, 72h, 14 days / 1 month

What “becoming aware” means in practice

The Commission guidance is central to the Cyber Resilience Act reporting obligations: a manufacturer need not have complete technical certainty before reporting. The trigger is when, after an initial assessment, the company can conclude with reasonable certainty that an actively exploited vulnerability exists or a severe incident has compromised the product. Article 3(41) defines an “exploitable vulnerability” as one that can be effectively used by an adversary under practical operational conditions — not merely in a lab or simulation. So you first need a well-defined threat model (architecture, intended purpose, foreseeable misuse, operating environment) to judge whether a vulnerability is practically exploitable, then check for evidence it is actually being exploited (telemetry, incident signals, customer reports, threat intelligence). Only when both hold do the clocks start — not merely when the manufacturer is first notified.

Cyber Resilience Act reporting obligations that do NOT apply in 2026

A frequent question: must manufacturers run active vulnerability monitoring from September 2026? No. Continuous vulnerability identification and the “no known exploitable vulnerabilities” duty stem from Annex I (Part I point 2(a)) and Article 13, which apply only from 11 December 2027. So in 2026 the Cyber Resilience Act reporting obligations do not require upstream reporting to suppliers (Article 13(6)), a dedicated single point of contact for users (Article 13(17)), or a full vulnerability-management policy (Annex I Part II). Per Article 71, only Article 14 applies early (11 September 2026); Chapter IV (Articles 35–51) applies from 11 June 2026; everything else from 11 December 2027.

Cyber Resilience Act reporting obligations timeline under the EU Cyber Resilience Act: 2026 vs 2027

Two horizons, two different capabilities

  • From 11 September 2026 — a reactive capability: assess credible indications and report actively exploited vulnerabilities or severe incidents within the deadlines. Continuous scanning, systematic monitoring or automated vulnerability intelligence are not required yet.
  • From 11 December 2027 — a proactive, comprehensive vulnerability-management system across the lifecycle, with monitoring of new vulnerabilities and full Annex I documentation.

● Article 14 is live on 11 September 2026 — full compliance follows 11 December 2027.

Rehearse the 24h/72h process with our CRA Incident Reporting Software, try our free CRA online check tool, or book a demo.

How COMPLYD helps you stay ahead

COMPLYD turns the Cyber Resilience Act reporting obligations into a rehearsed process — guided classification, risk-assessment workflows, composite-product assembly, conformity support, and lifecycle management with vulnerability and incident reporting — so you meet the 2026 reactive duty and are ready for the 2027 lifecycle obligations.

Frequently asked questions

What starts on 11 September 2026?

Only the Article 14 Cyber Resilience Act reporting obligations: reactive notification of actively exploited vulnerabilities and severe incidents via the Single Reporting Platform, plus user notification.

Do I need vulnerability management from 2026?

No. Continuous vulnerability management, a single point of contact and upstream reporting stem from Article 13 and Annex I, which apply from 11 December 2027.

When does the 24-hour clock start?

When, after an initial assessment, you conclude with reasonable certainty that a vulnerability is actively exploited or a severe incident has compromised the product — not merely when you are first notified.

Related to this article

Check for free

Does the Cyber Resilience Act apply to you? →

Product Check and Readiness Check, no login.

Glossary

Cyber Resilience Act glossary →

30 key terms explained, each with its legal reference.

Where does your product stand on the Cyber Resilience Act?

A first answer in minutes — or see the software that turns the legal text into a workflow.

Free CRA online checkExplore the CRA software


Last updated on 18 September 2026 · Sources: Regulation (EU) 2024/2847 (CRA) — EUR-Lex, ENISA — Single Reporting Platform

Alexander Aigner

About the author

Alexander Aigner

Product Security Expert, COMPLYD

Product security expert who has secured products in two of the most heavily regulated industries — medical and automotive. He helps teams meet the EU Cyber Resilience Act without slowing development.

LinkedIn profile