← CRA Glossary
CVD & Vulnerability Management

Actively Exploited Vulnerability

A CRA actively exploited vulnerability is a security flaw where threat actors currently use exploit code in real-world attacks. Under CRA Article 14, manufacturers must report actively exploited vulnerabilities to ENISA and the national CSIRT within 24 hours of becoming aware.

A CRA actively exploited vulnerability is a security flaw where threat actors currently use exploit code in real-world attacks. Under CRA Article 14, manufacturers must report actively exploited vulnerabilities to ENISA and the national CSIRT within 24 hours of becoming aware.

CVD & Vulnerability Management

Last updated 19 July 2026

What Is an Actively Exploited Vulnerability?

An actively exploited vulnerability is one for which credible evidence exists that it is being used by threat actors in real-world attacks - not merely demonstrated in a proof-of-concept or published as a theoretical risk, but actually weaponised against live systems. Evidence of active exploitation includes: threat intelligence reports from security researchers, ISACs, or vendors documenting exploitation attempts; incident response cases attributing attacks to a specific vulnerability; honeypot or telemetry data showing exploitation attempts in the wild; or inclusion in the CISA Known Exploited Vulnerabilities (KEV) catalogue. The distinction between theoretical and active exploitation matters significantly under the CRA because it triggers the most time-critical notification obligation.

CRA reference:Article 14

CRA Notification Requirements and Reporting Timelines

Article 14 of the CRA establishes mandatory reporting timelines when a manufacturer becomes aware of an actively exploited vulnerability in their product with digital elements:

  • Within 24 hours: Submit an early warning notification to ENISA and the designated CSIRT coordinator via the Single Reporting Platform (SRP), confirming active exploitation is occurring.
  • Within 72 hours: Submit a full notification including CVE identifiers, vulnerability details, affected versions, severity analysis, and initial mitigations.
  • Within 14 days: Submit a final report no later than 14 days after a corrective measure or mitigating update is available, detailing root causes and shipped patches.

These reporting timelines are statutory and begin from the moment the manufacturer has credible awareness of exploitation.

CRA reference:Article 14

Determining Exploitation Status: Sources and Signals

Manufacturers must establish mechanisms to monitor for exploitation evidence across multiple channels:

  • CISA KEV: The CISA Known Exploited Vulnerabilities catalogue is the most authoritative public source. Manufacturers should monitor it for vulnerabilities affecting their products' component stack.
  • Threat intelligence feeds: Commercial and open-source threat intelligence platforms aggregate exploitation indicators. Subscribing to feeds relevant to the product's technology stack is essential.
  • Security research publications: Exploit proof-of-concept publications on GitHub, Exploit-DB, or researcher blogs often precede or coincide with in-the-wild exploitation.
  • Incident telemetry: Manufacturers with cloud-connected products should monitor anomalous usage patterns that may indicate exploitation attempts.
  • National CSIRT alerts: EU national CSIRTs and ENISA regularly issue alerts for actively exploited vulnerabilities; subscribing to relevant alerting channels is good practice.
CRA reference:Article 14

Response Actions When Exploitation Is Detected

When a manufacturer becomes aware of active exploitation, the response should be immediate and parallel across three tracks:

Track 1 - Notification: Submit the CRA Article 14 notification to ENISA within 24 hours. Prepare follow-on notifications for the 72-hour and 14-day deadlines. Notify national CSIRT and relevant MSA if appropriate.

Track 2 - User protection: Publish an emergency security advisory with interim mitigation guidance (configuration changes, feature disablement, network controls) that users can apply immediately, even before a patch is available.

Track 3 - Remediation: Accelerate patch development, compress testing cycles where safely possible, and prepare the update delivery mechanism for rapid deployment. For exploited vulnerabilities, the normal remediation SLA should be overridden in favour of emergency response timelines.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

When exactly does the 24-hour CRA notification clock start?+

The 24-hour clock starts when the manufacturer 'becomes aware' of the active exploitation. This is defined as when the manufacturer has credible, actionable information that exploitation is occurring - not when they have fully confirmed or reproduced it. Manufacturers should err on the side of early notification when in doubt: submitting a notification that is later revised is far better than missing the 24-hour deadline. The initial notification does not need to be a complete technical analysis.

What if active exploitation is discovered through a third party's incident, not the manufacturer's own systems?+

The notification obligation triggers regardless of where exploitation evidence is first observed. If a customer reports that their deployment of your product is being attacked via a specific vulnerability, or if a CSIRT notifies you that your product's vulnerability is being exploited in the wild, the 24-hour clock starts from that notification. Manufacturers should treat third-party exploitation reports as high-priority alerts and initiate their emergency response process immediately.

Is a proof-of-concept exploit the same as active exploitation for CRA purposes?+

No. A published proof-of-concept (PoC) demonstrates that exploitation is theoretically possible but does not constitute evidence of actual attacks occurring. A PoC publication significantly raises the exploitation risk and typically triggers escalated remediation priority and EPSS score increases. However, the CRA's 24-hour notification obligation applies specifically to active exploitation - evidence that attacks are actually happening. Manufacturers should accelerate response upon PoC publication without necessarily treating it as the same trigger as confirmed exploitation.

Sector checklists covering Actively Exploited Vulnerability

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Smart Home DevicesSmart home devices, such as thermostats, smart speakers, lighting controllers and home security cameras, are among the most common products with digital elements in scope for the CRA. Thermostats and lighting controllers are default class, and Module A internal control is open to them (Article 32(1)). A smart speaker with a general purpose virtual assistant is Important Class I (Annex III, point 16). A home security camera, smart lock, baby monitor or alarm system is Important Class I (Annex III, point 17). So is a hub or software that centrally controls these security products.Industrial Controllers & PLCsIndustrial controllers, PLCs, and SCADA components are default-class products under the CRA, because classification follows core functionality (Article 7(1)) and Annex III lists no industrial control category. They can use Module A internal control (Article 32(1)). These products have long operational lifetimes (10–20+ years), network connectivity, and significant safety implications. These facts raise the risk that the Article 13(2) risk assessment must address. Article 14 reporting applies from 11 September 2026, and the conformity obligations apply from 11 December 2027.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Actively Exploited Vulnerability fits into your complete CRA compliance programme.

View checklists →