# CRA vulnerability reporting: the 24-hour rule, step by step

URL: https://sbombox.com/blog/cra-24-hour-reporting
By SBOMBox SBOM experts. Published 2026-07-01, updated 2026-11-13

> What CRA reporting requires since 11 September 2026: what triggers a report, the 24-hour, 72-hour and final deadlines, where reports go and how to be ready.

Short answer: since 11 September 2026, manufacturers must report every actively exploited vulnerability and every severe incident affecting their products. Send an early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days of a fix being available (one month after the notification for an incident). Reports go through ENISA's Single Reporting Platform to the national CSIRT acting as coordinator, and ENISA sees them at the same time. This applies to products already on the market, not only new ones.

## What triggers a report

- An actively exploited vulnerability in your product, including in a component inside it (Article 14(1)). A vulnerability that is known but not exploited does not trigger a mandatory report, though you may report it voluntarily under Article 15.
- A severe incident having an impact on the security of your product (Article 14(3)). An incident is severe if it affects, or could affect, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or if it has led or could lead to malicious code running in the product or in a user's systems (Article 14(5)).

## The three deadlines

> an early warning notification of an actively exploited vulnerability, without undue delay and in any event within 24 hours of the manufacturer becoming aware of it
>
> — Regulation (EU) 2024/2847, Article 14(2)(a)

**CRA reporting deadlines under Article 14**

| Step | Actively exploited vulnerability | Severe incident | What it must contain |
| --- | --- | --- | --- |
| Early warning | Within 24 hours of becoming aware | Within 24 hours of becoming aware | Where applicable, the Member States where the product is available. For incidents, whether it is suspected to be caused by unlawful or malicious acts |
| Notification | Within 72 hours of becoming aware | Within 72 hours of becoming aware | General information about the product, the nature of the exploit or incident, corrective or mitigating measures taken and those users can take, and how sensitive you consider the information |
| Final report | No later than 14 days after a corrective or mitigating measure is available | Within one month of the incident notification | Vulnerability: description, severity and impact, information on any malicious actor, details of the fix. Incident: detailed description, likely root cause, applied and ongoing mitigations |

Each later step is needed only 'unless the relevant information has already been provided', so a complete early warning can shorten the work. The coordinating CSIRT may also ask for an intermediate status report (Article 14(6)).

## Where the report goes

Every report is submitted through the Single Reporting Platform run by ENISA (Article 16), using the electronic notification end-point of the CSIRT designated as coordinator in the Member State of your main establishment. Article 14(7) defines that as the Member State 'where the decisions related to the cybersecurity of its products with digital elements are predominantly taken'. If that cannot be determined, it is the Member State where you have the most employees in the EU.

Manufacturers with no main establishment in the EU use the first of these that applies:

- the Member State of the authorised representative acting for the highest number of your products;
- otherwise, the Member State of the importer placing the highest number of your products on the market;
- otherwise, the Member State of the distributor making the highest number of your products available;
- otherwise, the Member State with the highest number of users of your products.

For accounts, access and what the platform accepts, see our guide to [ENISA's Single Reporting Platform](https://sbombox.com/blog/enisa-cra-single-reporting-platform).

## You must also tell your users

Reporting to authorities is half the duty. Under Article 14(8), after becoming aware of an actively exploited vulnerability or severe incident you must inform the impacted users, and where appropriate all users, together with any mitigation they can apply, 'where appropriate in a structured, machine-readable format that is easily automatically processable'. In practice that means a security advisory, ideally in CSAF with a VEX profile; see [CSAF vs VEX](https://sbombox.com/blog/csaf-vs-vex-security-advisories). If you do not inform users in time, the CSIRT may do it for you.

## Products already on the market

Reporting is the one CRA duty that reaches back in time. Article 69(3) applies Article 14 to every in-scope product placed on the market before 11 December 2027. A router sold in 2022 that is still in use is covered today. The full timeline is in [CRA deadlines](https://sbombox.com/blog/cra-key-dates).

## Why the SBOM decides whether you can meet 24 hours

The early warning needs one fact quickly: which of your products and versions contain the exploited component. With a searchable SBOM for every released version, that is a query. Without one, it is days of digging through build logs. Teams that rehearse this usually find the form is easy and the inventory is the bottleneck.

## Who owns each step

- Detection: whoever watches vulnerability feeds and the CISA Known Exploited Vulnerabilities catalogue against your SBOMs.
- Confirmation: an engineer who can say which releases contain the component and whether it is reachable.
- Submission: a named owner and a deputy, both with platform access. Twenty-four hours includes weekends and public holidays.
- User communication: whoever publishes advisories and VEX statements.

## Readiness checklist

- An SBOM for every released version, stored where you can search across products. Check yours with the [free SBOM checker](https://sbombox.com/audit).
- Exact component versions, not ranges, so vulnerability matching is reliable. See the [SBOM minimum elements](https://sbombox.com/blog/sbom-minimum-elements).
- [VEX](https://sbombox.com/blog/what-is-vex) statements recording which vulnerabilities do and do not affect each product.
- Your coordinating CSIRT identified and platform accounts set up.
- A short early-warning template: product, affected versions, Member States where it is sold, what you know, suspected malicious activity, immediate mitigation.
- A tabletop exercise on a recent high-profile CVE, timed end to end.

Micro and small enterprises cannot be fined for missing the 24-hour early-warning deadline (Article 64(10)(a)), but every other part of the duty still applies to them, and the later deadlines are enforced.

## Frequently asked questions

### What is the CRA 24-hour reporting rule?

Under Article 14 of the Cyber Resilience Act, a manufacturer must send an early warning within 24 hours of becoming aware of an actively exploited vulnerability or severe incident affecting its product, followed by a notification within 72 hours and a final report.

### When did CRA reporting start?

11 September 2026. It applies to all in-scope products, including those placed on the market before the rest of the CRA applies on 11 December 2027.

### Where do I report a vulnerability under the CRA?

Through ENISA's Single Reporting Platform, using the end-point of the CSIRT designated as coordinator in the Member State of your main establishment in the EU. ENISA receives the report at the same time.

### Do I have to report vulnerabilities that are not being exploited?

No. Mandatory reporting covers actively exploited vulnerabilities and severe incidents. Other vulnerabilities, cyber threats and near misses can be reported voluntarily under Article 15.

### Does the 24 hours include weekends?

Yes. The regulation counts 24 hours from when you become aware, with no exception for weekends or public holidays, so plan a rota.

### What if I do not have all the details within 24 hours?

Send the early warning with what you know. The 72-hour notification and the final report add the detail, and later steps are only needed for information you have not already provided.

This is general information, not legal advice. Confirm how the rules apply to you with counsel.
