Two engineers at a desk reviewing code together on a large monitor

PSIRT & disclosure

CRA vulnerability reporting: the 24-hour early warning, 72-hour notification and final report

Last updated:

Under the Cyber Resilience Act, a manufacturer that becomes aware of an actively exploited vulnerability or a severe incident affecting its product must send an early warning within 24 hours, a notification within 72 hours, and a final report later. Everything goes through the ENISA Single Reporting Platform to the national CSIRT coordinator and ENISA at the same time. This has applied since 11 September 2026.

For the full picture of the regulation, see the Cyber Resilience Act hub.

Key takeaways

  • For the full picture of the regulation, see the Cyber Resilience Act hub.
  • A researcher's report of a bug nobody has exploited is not a mandatory notification.
  • > Two timestamps, not one.
  • Yes, when it is exploited in your product.

What triggers a mandatory report?

Trigger Definition in the CRA
Actively exploited vulnerability A vulnerability for which there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission (Art. 3)
Severe incident affecting product security An incident that harms, or can harm, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led or can lead to malicious code being introduced or executed in the product or the user's systems (Art. 14(5))

A researcher's report of a bug nobody has exploited is not a mandatory notification. You handle it through coordinated vulnerability disclosure, fix it under Annex I Part II, and may notify it voluntarily (Art. 15).

The clock starts when you become aware, whether the evidence comes from a researcher, a customer, a CSIRT, threat intelligence or your own telemetry.

When does the 24-hour clock start?

It starts at the moment you reach a reasonable degree of certainty, after a prompt initial assessment, that a vulnerability in your product is being actively exploited or that a severe incident has compromised its security. That is how the Commission guidance on the CRA (C(2026) 5252, 27 July 2026, para 213) reads "becoming aware". Before that point you are investigating. After it, you have 24 hours.

Two timestamps, not one. Log the time of the first signal and the time of awareness separately. The guidance accepts that confirming exploitation can take time in some cases, but expects prompt action on the initial assessment, especially for high-risk vulnerabilities (para 214).

The Commission FAQs on the CRA (version 1.4, section 5.1) give typical ways a manufacturer becomes aware:

  • a customer or partner reports unusual activity or a compromise;
  • a researcher, security firm or government agency reports exploitation of your product;
  • an ethical hacker reports a flaw that is already exploited in the wild;
  • your own telemetry, honeypots or threat monitoring show exploitation.

The FAQ adds that the CRA does not oblige you to monitor all of these channels. Exploitation you knew about before 11 September 2026 does not have to be reported retroactively. A known vulnerability whose exploitation you learn about after that date does (guidance para 217).

Does a vulnerability in a third-party component count?

Yes, when it is exploited in your product. The duty covers vulnerabilities "contained in" your product, so a library or SDK inside your firmware counts. The component's own manufacturer must also notify if it placed that component on the market (FAQ 5.4).

Scenario Mandatory Art. 14 notification for you? What still applies
Reliable evidence that a component flaw was exploited in your product Yes Report upstream (Art. 13(6)), inform users (Art. 14(8))
The component's CVE is in CISA's KEV catalog, with no evidence of exploitation in your product No, on that basis alone (guidance para 218) Fix under Annex I Part II; keep watching for evidence
The flaw cannot be exploited in your product, for example unreachable code No (para 218, FAQ 5.4) Report upstream; record a VEX "not affected" statement
A researcher reports a zero-day with no sign of malicious use No (FAQ 5.2) Handle it through CVD; voluntary notification possible (Art. 15)

Upstream reporting covers the component version you integrate; you can skip it if the maintainer already knows or there is none (guidance paras 223–225). KEV and EPSS help rank the backlog: see KEV and EPSS prioritisation.

The three reports for an exploited vulnerability

Report Deadline Minimum content (Art. 14(2))
Early warning Without undue delay, at most 24 hours after awareness That an actively exploited vulnerability exists; where applicable, the Member States where the product is made available
Vulnerability notification At most 72 hours after awareness General information on the product, the nature of the exploit and vulnerability, corrective or mitigating measures taken and those users can take, and how sensitive you consider the information
Final report At most 14 days after a corrective or mitigating measure is available Description, severity and impact; information on the malicious actor where available; details of the security update or other corrective measures

The three reports for a severe incident

Report Deadline Minimum content (Art. 14(4))
Early warning At most 24 hours after awareness Whether the incident is suspected to be caused by unlawful or malicious acts; where applicable, the Member States where the product is available
Incident notification At most 72 hours after awareness Nature of the incident, initial assessment, corrective or mitigating measures taken and those users can take, sensitivity
Final report Within one month after the 72-hour notification Detailed description, severity and impact; likely threat type or root cause; applied and ongoing mitigations

The CSIRT may also ask for an intermediate report on status updates (Art. 14(6)).

Where to send it

  • Channel: the Single Reporting Platform established by ENISA under Article 16. ENISA deployed its initial operating capability on 11 September 2026; the portal is at portal.cra-srp.enisa.europa.eu.
  • Recipient: the CSIRT designated as coordinator in the Member State of your main establishment in the EU, meaning where cybersecurity decisions for your products are mainly taken (or, failing that, where you have the most EU employees). ENISA receives the notification simultaneously (Art. 14(7)).
  • Non-EU manufacturers use the CSIRT of the Member State determined in this order: where your authorised representative for most of your products is established; else your importer for most products; else your distributor for most products; else where most of your users are located.
  • The receiving CSIRT shares the notification with the CSIRTs of the Member States where the product is available. It can delay that only in exceptional, justified cases (Art. 16(2)).

How do you file on the Single Reporting Platform, step by step?

You file through the SRP web interface with a personal EU Login account. The steps follow ENISA's registration guidance and submission guidance, both last updated on 12 September 2026.

Platform status on 13 November 2026. ENISA's SRP page states that the SRP was upgraded to version 1.3 on 4 November 2026 and that its documentation is being updated to match, so check the release date of each guide before you file. The same page links a CRA SRP Status page that shows whether the platform is available, and the FAQ was last updated on 15 October 2026.

  1. Have an EU Login account with multi-factor authenticationAccounts are personal; create them in advance.
  2. Register as Primary Assigned Representative (AR)Open the portal and choose the AR role. Select the CSIRT designated as coordinator under Article 14(7), log in, accept the legal agreement and enter the manufacturer's details. The CSIRT validates the AR-manufacturer link afterwards. You can submit while it is pending.
  3. Submit the early warningChoose "Submit new notification", pick actively exploited vulnerability or severe incident, and complete the Early Warning tab. Drafts are visible only to the person who saved them.
  4. Add the 72-hour notificationto the same record, in the 72-hour Notification tab. This is where you invoke Particularly Exceptional Circumstances under Article 16(2), if you rely on them.
  5. Add the final reportin the Final Report tab. After that, the notification can no longer be edited.

SRP behaviour to plan around (ENISA FAQ, 15 October 2026). One Primary AR and up to 20 Secondary ARs per manufacturer. Secondary ARs can only be invited once the Primary AR is "Verified", and invitations expire after 7 days. ENISA advises registering only when a notification is due. The initial release has no API and an English-only interface. If the SRP is unavailable, contact your CSIRT directly if needed, and file on the SRP once it is back (FAQ 9, 15, 24, 25).

How do an SBOM, VEX and a PSIRT make the 24-hour clock workable?

They turn the first 24 hours into a lookup and one decision, not an investigation from zero. The SBOM tells you which releases contain the component, VEX records where it is or is not exploitable, and the PSIRT owns the decision and the filing.

  • An SBOM per release. Annex I Part II(1) already requires manufacturers to draw up an SBOM "in a commonly used and machine-readable format covering at the very least the top-level dependencies" (CRA text, EUR-Lex). CycloneDX and SPDX are both widely used formats. Kept per firmware version, as in our firmware SBOM guide, it answers "which models and versions ship this library?" in minutes. That is the scope the early warning and the 72-hour notification need.
  • A VEX statement per vulnerability. VEX says whether, and why, a product is affected. The VEX profile in OASIS CSAF 2.0 (OASIS Standard, 18 November 2022) uses four product states: fixed, known_affected, known_not_affected and under_investigation. A known_not_affected entry with its justification is the written record behind a "no notification" decision for unreachable code (guidance para 218). A CSAF advisory is also one machine-readable way to inform users under Art. 14(8).
  • A PSIRT with a named owner. Someone on call applies the triage rule, signs off "actively exploited", and holds the SRP account. Without that role, the data sits unused while the clock runs.

In the hypothetical example below, they let the early warning go out three and a half hours after awareness.

Tell your users too

You must also inform impacted users, and where appropriate all users, about the exploited vulnerability or incident and the mitigations they can apply, where appropriate in a structured, machine-readable format (Art. 14(8)). If you do not do this in time, the CSIRT may inform users itself.

What to prepare before the first incident

  1. A triage rulethat defines "reliable evidence of exploitation" for your products, and who signs off.
  2. An on-call rosterthat covers weekends and holidays. A 24-hour deadline does not pause.
  3. Product data ready to paste: model names, firmware versions, the Member States where each is sold, and the SBOM per version.
  4. SRP readiness: at least two people with their own EU Login accounts and MFA, the coordinating CSIRT already identified, and ENISA's user manual read. Because ENISA advises registering only when a notification is due, plan for the first filing to be made by the Primary AR alone.
  5. Pre-written templatesfor the early warning, 72-hour notification, final report and user advisory.
  6. Evidence logging: when you became aware, what you knew, and what you sent. Authorities will look at the timeline.

To see which of these pieces you already have, run the free CRA readiness check. It is a self-reported indicator against eight Annex I-derived categories and runs in your browser.

Worked example: what does a 24h/72h/final timeline look like?

The incident below is hypothetical. A maker of building-automation controllers with its main EU establishment in one Member State sells in six. A customer reports devices rebooting and an unknown process running.

When (illustrative) What happens CRA step
Day 0, 09:00 Customer report with logs reaches the security contact First signal logged
Day 0, 11:30 Triage confirms an attacker ran code through a flaw in the bundled web-server component, without the owner's permission Awareness: the 24 h and 72 h clocks start
Day 0, 12:00 The SBOM lookup shows firmware 3.1 to 3.4 contain the vulnerable version Scope for the reports
Day 0, 15:00 The Primary AR registers and files the early warning, listing the six Member States Art. 14(2)(a), due by Day 1, 11:30
Day 2 72-hour notification with the nature of the exploit and the mitigations (disable remote UI, firewall rule), plus an advisory to users Art. 14(2)(b), due by Day 3, 11:30; Art. 14(8)
Day 2 Report to the component's maintainer Art. 13(6)
Day 12 Firmware 3.5 with the fix is released Corrective measure available
By Day 26 Final report: description, severity, impact, attacker information if known, update details Art. 14(2)(c), 14 days after the fix

After the fix, ENISA may add the vulnerability to the European vulnerability database in agreement with the manufacturer (Art. 17(5)).

Common mistakes

  • Waiting for a patch before the early warning. The 24-hour report does not need a fix; the final report comes after the fix.
  • Treating only your own code as relevant. A vulnerability in a third-party library inside your firmware is a vulnerability in your product.
  • Forgetting legacy models. Products placed on the market before 11 December 2027 are covered by Article 14 too.
  • Assuming reporting ends with support. Article 14 reporting continues after the support period ends (guidance para 210).
  • Picking the wrong CSIRT. ENISA says such a notification may be invalidated and must be resubmitted to the correct one (FAQ 18).
  • Trusting the SRP countdown. As of 15 October 2026, the 72-hour counter shows a due time 48 hours after the early warning, and there is no counter for the final report on an exploited vulnerability (FAQ 26). Your legal deadline runs from awareness.

Fines and the small-company carve-out

Breaching Article 14 falls under the highest fine band: up to EUR 15 million or 2.5% of worldwide annual turnover (Art. 64(2)). Micro and small enterprises are not fined for missing the 24-hour early-warning deadline (Art. 64(10)), but they still have to report.

Where AI speeds up the 72-hour notification, not the 24-hour judgment call

Deciding whether a report meets the "actively exploited" bar within 24 hours is a human judgment call the rules keep with the manufacturer; no automated scan should make that call. Once that threshold is confirmed, the 72-hour notification and the final report need the same product, component and CVE detail SoftWSP's firmware scan already extracts and matches against CVE, KEV and EPSS data. AI drafts a plain-language report from those matches (which component, which fix, which affected versions), with every claim citing its evidence. An engineer or PSIRT analyst adapts it into the notification, reviews it and submits it. The AI narrates evidence the scan already produced and does not decide that a vulnerability is actively exploited.

SoftWSP runs intake, triage and CRA notifications for device makers that have no in-house PSIRT: see PSIRT as a service. For the wider task list, use the CRA checklist for device makers.

This guide is general information, not legal advice.

Put this guide to work

Frequently asked questions

When does the CRA 24-hour reporting obligation apply?

Article 14 has applied since 11 September 2026. It covers all in-scope products, including those placed on the EU market before 11 December 2027.

What must be reported within 24 hours?

An early warning for any actively exploited vulnerability in your product, and for any severe incident affecting its security, within 24 hours of becoming aware of it.

Where do I submit CRA notifications?

Through the Single Reporting Platform run by ENISA, using the electronic end-point of the CSIRT designated as coordinator in the Member State of your main EU establishment. The notification is made available to ENISA at the same time.

Does every vulnerability report need to be notified?

No. The mandatory duty covers actively exploited vulnerabilities, meaning there is reliable evidence a malicious actor exploited it without the system owner's permission, and severe incidents. Other vulnerabilities can be notified voluntarily.

Can a small company be fined for missing the 24-hour deadline?

Article 64(10) states that administrative fines are not applied to micro and small enterprises for missing the 24-hour early-warning deadline. The other obligations still apply.

Sources

  1. Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20 November 2024, Articles 14, 16, 64 and Annex I Part II, EUR-Lex
  2. European Commission: CRA reporting obligations
  3. ENISA: The CRA Single Reporting Platform is launched (11 September 2026)
  4. ENISA: Single Reporting Platform (SRP) topic page (SRP version 1.3 note dated 4 November 2026; retrieved 13 November 2026)
  5. ENISA: CRA Single Reporting Platform – Frequently Asked Questions (updated 15 October 2026)
  6. ENISA: CRA SRP Guidance – AR User Registration (updated 12 September 2026)
  7. ENISA: CRA SRP Guidance – AR Notification submission and update (updated 12 September 2026)
  8. European Commission: Guidance to support timely Cyber Resilience Act implementation (C(2026) 5252, 27 July 2026)
  9. European Commission: FAQs on the Cyber Resilience Act (version 1.4, 4 September 2026)
  10. ENISA: CRA SRP Status (retrieved 13 November 2026)
  11. OASIS: Common Security Advisory Framework (CSAF) Version 2.0, OASIS Standard, 18 November 2022, Profile 5: VEX
Was this guide helpful?

In this cluster

CRA vulnerability reporting: the 24-hour early warning, 72-hour notification and final report