Definition

What is an actively exploited vulnerability?

Actively exploited vulnerability · also: Exploited in the wild, Actively exploited CVE

Short answer

A vulnerability with reliable evidence that attackers ran malicious code on a system without the owner's permission — the trigger for CRA Article 14 reporting.

A vulnerability for which there is reliable evidence that execution of malicious code was performed by an actor on a system without the permission of the system owner. Reliable evidence may come from the manufacturer's own telemetry, a customer report, a researcher, a CSIRT or an exploitation catalogue such as CISA KEV. Once the manufacturer becomes aware, Article 14 requires an early warning within 24 hours, a notification within 72 hours and a final report within 14 days of a corrective measure becoming available.

In plain terms, 'actively exploited' means attackers are already using the flaw against real systems. It is a statement about observed events, not about severity or likelihood: a public proof-of-concept, a critical CVSS score or a high EPSS probability make exploitation more likely, but none of them is evidence that it has happened.

For a manufacturer the reporting question has two parts: is there reliable evidence of exploitation, and is the vulnerability contained in the product in a form that matters? A vulnerable library that is shipped but never loaded is a different case from one on the product's network-facing path. Record the evidence, the reasoning (a VEX statement with its justification works well) and the time a responsible person confirmed it — that timestamp is the awareness time every deadline runs from.

Reference: Art. 3(42); Art. 14(1)–(3)

Updated · Paraphrase for orientation, not legal advice.

Share:LinkedInXE-mail

Frequently asked questions

What does 'actively exploited' mean for a CVE?
There is reliable evidence that attackers have used the vulnerability against a real system without the owner's permission. A CVE can be critical, have public exploit code or a high EPSS score and still not be actively exploited; a medium-severity CVE can be exploited in the wild.
Is every CVE in the CISA KEV catalogue reportable under the CRA?
Not automatically. A KEV listing is strong evidence of exploitation in the wild, so a KEV-listed vulnerability in a component you ship should open an immediate reportability review. Whether you must notify depends on whether the vulnerability is contained in your product; document the assessment, the evidence and the awareness time either way.
What are the CRA deadlines for an actively exploited vulnerability?
An early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available — submitted through ENISA's single reporting platform to the coordinator CSIRT and ENISA.
Where does evidence of active exploitation come from?
Your own telemetry and incident response, customer or researcher reports, CSIRT and vendor advisories, threat-intelligence feeds and exploitation catalogues such as CISA KEV. Record the source and arrival time of each piece of evidence.

In practice

Related terms

Know your Article 14 deadlines before you need them.

Enter an awareness time and get the 24-hour, 72-hour and final-report deadlines in your timezone.