Regulatory Compliance

CRA Article 14 Is Live: What the September 2026 Reporting Deadline Means for Your Organisation

· Regonance Cybersecurity · 9 min read

Article 14 of the EU Cyber Resilience Act (Regulation (EU) 2024/2847) has been binding since 11 September 2026. Manufacturers of products with digital elements must now report actively exploited vulnerabilities to ENISA's Single Reporting Platform within 24 hours of becoming aware, and notify severe security incidents through a parallel reporting track. This is not a preparation milestone — it is a hard enforcement date, with penalties up to €15 million or 2.5% of worldwide annual turnover.

This article explains what Article 14 requires, who must comply, and how a structured suspicious email reporting process helps manufacturers meet these obligations.

What Changed on 11 September 2026

The Cyber Resilience Act entered into force in December 2024, but its obligations phase in over time. Most requirements — including product-level cybersecurity standards, conformity assessment, and CE marking — do not apply until 11 December 2027.

Article 14 is different. Its reporting obligations apply now, and they apply to all products with digital elements currently on the EU market — including products placed on the market years before the CRA existed.

This means manufacturers who planned to start preparing for the CRA in 2027 are already behind on their reporting obligations.

The Two Reporting Triggers

Article 14 establishes two independent reporting obligations. Each has its own trigger and timeline.

Trigger 1: Actively Exploited Vulnerabilities

A manufacturer must notify ENISA when it becomes aware of an actively exploited vulnerability contained in one of its products. An "actively exploited vulnerability" means that a threat actor has used the vulnerability to compromise a system in the real world — it is not a theoretical risk assessment.

Reporting timeline for actively exploited vulnerabilities:

StageDeadlineContent
Early warning24 hours from awarenessConfirmation of the vulnerability, product affected, known exploitation
Full notification72 hours from awarenessTechnical details, scope, indicators of compromise
Final report14 days from corrective measure being availableComplete analysis, corrective measures, mitigation guidance

Trigger 2: Severe Security Incidents

A manufacturer must also notify any severe incident that affects the security of its product with digital elements. This covers incidents beyond vulnerability exploitation — including supply chain compromises, infrastructure breaches affecting product integrity, or attacks targeting the manufacturer's development or update delivery systems.

Reporting timeline for severe incidents:

StageDeadlineContent
Early warning24 hours from awarenessConfirmation of incident, suspected cause, product impact
Full notification72 hours from awarenessImpact assessment, containment actions, scope
Final report1 month from notificationRoot cause, full remediation, lessons learned

An event can satisfy one trigger, both, or neither. Each must be assessed separately.

Who Must Report

The reporting obligation falls on the manufacturer — not the customer, not the operator, and not the distributor. Under the CRA, the manufacturer is the entity that places the product with digital elements on the EU market or puts it into service under its own name or trademark.

Critically, Article 14 applies to all products with digital elements on the EU market, including:

  • Products placed on the market before December 2027
  • Legacy firmware and embedded devices with long lifecycles
  • Software products, whether distributed as packages or delivered as updates
  • Connected hardware devices

If your product is on the EU market and contains digital elements, Article 14's reporting obligation applies today.

How Suspicious Email Reports Surface CRA-Relevant Intelligence

Manufacturers often learn about actively exploited vulnerabilities through external channels: security researchers, CSIRTs, customer reports, or threat intelligence feeds. But a significant and underappreciated source of vulnerability intelligence comes from internal email reporting.

Suspicious email reports can reveal CRA-reportable events in several ways:

Phishing campaigns targeting your product's users. When customers or users forward suspicious emails that impersonate your product or brand, those reports may indicate that attackers are exploiting a vulnerability in your product to harvest credentials or deliver malware.

Supply chain compromise indicators. Suspicious emails that spoof your vendors or development partners may signal that an attacker has compromised your supply chain — which is a severe security incident under Article 14.

Internal compromise signals. Employees reporting suspicious emails that target development, build, or deployment systems may be the first indicator of an attack on your product delivery infrastructure.

Vulnerability disclosure via email. Security researchers sometimes report vulnerabilities directly via email rather than through formal disclosure channels. Without a structured email reporting process, these reports may be lost or delayed — each hour of delay compresses the 24-hour reporting window.

The Penalty Framework

Violations of Article 14 fall within the highest penalty tier under the CRA:

  • Up to €15 million or 2.5% of worldwide annual turnover, whichever is greater
  • Penalties apply to reporting failures independently — you can face sanctions for failing to report even if the underlying vulnerability or incident is subsequently resolved
  • Article 14(8) additionally requires manufacturers to notify affected users of vulnerabilities and incidents; failure to do so allows the receiving CSIRT to notify users directly

The penalty provisions under Article 64 do not themselves apply early (they become enforceable with the full CRA in December 2027), but the reporting obligation is legally binding now. Reports filed — or not filed — in 2026 and 2027 will form the regulatory record that authorities examine once enforcement begins.

Connecting Email Reporting to CRA Compliance

For manufacturers subject to Article 14, the Every Report Matters methodology provides a framework to ensure that vulnerability intelligence reaches the right people within the 24-hour window:

Recognise and Report: Employees, customers, and security researchers must have a clear, easy-to-find channel to report suspicious activity or potential vulnerabilities. The CRA itself requires manufacturers to maintain an accessible intake channel for vulnerability reporting.

Receive and Preserve: Reports must be captured with their full context — headers, metadata, timestamps. A vulnerability report that arrives by email and is casually forwarded loses the technical detail needed for CRA notification.

Assess: Triage must determine whether the report indicates an actively exploited vulnerability or a severe incident. This assessment directly maps to the Article 14 reporting triggers.

Investigate and Respond: The investigation produces the technical detail required for the 72-hour notification and the 14-day final report.

What to Do Now

If you manufacture or distribute products with digital elements on the EU market:

1. Confirm your reporting channel to ENISA. Article 14 notifications go through ENISA's Single Reporting Platform (SRP). Confirm access and test the submission process before you need it under pressure.

2. Establish internal reporting channels. Employees, customers, and security researchers need a visible, easy-to-use way to report suspicious activity and potential vulnerabilities. This is both a CRA best practice and a requirement under the broader regulation.

3. Build a triage process that identifies CRA triggers. Your assessment workflow must determine whether a report indicates an actively exploited vulnerability or a severe incident — the two Article 14 triggers — within hours, not days.

4. Preserve everything. Every report, every assessment, every notification decision. Article 14 creates a regulatory record. The absence of records is itself evidence of non-compliance.

5. Map the regulatory overlap. The same incident may trigger notifications under CRA, NIS2, GDPR, and potentially DORA. A single reporting lifecycle that feeds multiple notification streams prevents duplication and ensures nothing is missed.

Frequently Asked Questions


This article is part of the Every Report Matters knowledge series by Regonance Cybersecurity. For the complete methodology and implementation guidance, explore the Reporting Readiness Kit, the Complete Reporting Playbook, or the Organisational Implementation Package.

Related articles:

Download the free Every Report Matters Methodology Brief — understand what structured reporting delivers before you implement. → Download (email required)

Download the free Every Report Matters Methodology Brief

The reporting gap, the 9-stage lifecycle, and why EU regulation now makes this urgent. 11 pages.

We publish practical cybersecurity reporting articles. No spam. Unsubscribe with one click.