Actively exploited vulnerability

An actively exploited vulnerability is a flaw that attackers have demonstrably already used. Once a manufacturer becomes aware of one, the Article 14 reporting obligation starts with a 24-hour deadline.

Definition

Actively exploited vulnerability: definition

§

Under Article 3(42) of Regulation (EU) 2024/2847, this is the case when there is reliable evidence that a malicious actor has exploited the vulnerability in a system without permission of the system owner. The regulation distinguishes it from a vulnerability in general (point 40) and an exploitable vulnerability (point 41), which could be used under practical operational conditions.

Only evidence of actual exploitation triggers the reporting obligation. Reports go through the Single Reporting Platform, simultaneously to the competent CSIRT and to ENISA.

Actively exploited vulnerability under the Cyber Resilience Act: how COMPLYD implements it

In practice

Actively exploited vulnerability in practice

Evidence can come from your own telemetry, customer reports, security researchers or lists such as the Known Exploited Vulnerabilities Catalog of the US agency CISA. Penetration tests commissioned by the manufacturer do not count, because no one is acting maliciously or without permission.

The 24-hour clock starts when the manufacturer becomes aware. Assessing a tip-off therefore has to be a defined process in itself: who checks, how fast, and who decides whether the evidence is reliable?

Example

A customer reports unknown accounts on several of its VPN gateways. Analysis shows attackers used a flaw in the login. From that moment the manufacturer has 24 hours for the early warning, 72 hours for the notification and, once a patch is available, 14 days for the final report.

What to do

  • Define intake channels for tip-offs: contact address, support, telemetry, threat intelligence
  • Set criteria for when evidence counts as reliable
  • Set up an on-call rota that can report within 24 hours at weekends too
  • Register and test access to the Single Reporting Platform in advance
Set straight

Common misconceptions

Myth

“A high CVSS score makes a flaw reportable.”

In fact

Severity plays no role for the reporting obligation. What matters is evidence of actual exploitation.

Myth

“We report once the patch is ready.”

In fact

The early warning is due within 24 hours, whether or not a fix exists yet.

More in the glossary

Related terms

Article 14

Reporting deadlines

The three stages from early warning to final report.

Read the entry
Article 16

Single Reporting Platform (SRP)

The channel through which the report is submitted.

Read the entry
Article 14(5)

Severe incident

The second trigger for reporting, with its own final report deadline.

Read the entry
Stephan Hutterer
About the author

Stephan Hutterer

Founder & CEO, COMPLYD

Product-security specialist with 20+ years protecting critical OT systems and deep IEC 62443 expertise. He founded COMPLYD to turn the EU Cyber Resilience Act into a workable process for product teams.

LinkedIn profile

Next step

Where does your product stand on the Cyber Resilience Act?

The free Product Check shows within minutes which of your products are in scope. The Readiness Check shows how well your company is prepared for the obligations.

Free, no login, no email. See who is in scope or go straight to the compliance software.