# CRA Vulnerability Reporting Began on 11 September 2026: The Evidence a QA Team Must Be Able to Produce

Dokimore Security Team · October 28, 2026, updated 2026-11-01 · 7 min read

Format: Explainer · Written for: Security and compliance reviewers, QA leads and test managers, Engineering managers · Where it applies: [Ireland](https://dokimore.com/for/ireland), [Germany](https://dokimore.com/for/germany), [France](https://dokimore.com/for/france), [Netherlands](https://dokimore.com/for/netherlands). The Cyber Resilience Act binds manufacturers that place products with digital elements on the EU market, wherever the company is based; reports go through the platform ENISA runs. Whether a product is in scope is a question for counsel.

> Twenty-four hours from awareness to the early warning, seventy-two to the notification, fourteen days from the fix to the final report. The clock does not wait for the ticket to be triaged.

## In short

- The Cyber Resilience Act’s reporting obligation applies from 11 September 2026, while the Act’s main obligations apply from 11 December 2027. A manufacturer that becomes aware of an actively exploited vulnerability in its product files an early warning within 24 hours, a notification within 72 hours and a final report no later than 14 days after a corrective measure is available, through the platform ENISA runs.
- The clock starts at awareness, so the work that decides whether a report is accurate happens before it: being able to reproduce the exploit, name the affected versions, show the fix closed it and reconstruct who knew what and when.
- A QA team that already keeps evidence per finding, the request, the response, the proof of concept and the re-scan that shows it closed, has most of the record. The gap is usually the timeline and the ownership of the decision, which belong in a written process, not a tool.

## What applies, and to whom

The Cyber Resilience Act, Regulation (EU) 2024/2847, entered into force on 10 December 2024 and applies to products with digital elements placed on the EU market: software and hardware with a network connection, from a device’s firmware to a developer library. Its main obligations, the design requirements, conformity assessment and CE marking among them, apply from 11 December 2027. One part came first. From 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents that affect the security of their product. Open-source software stewards, a category the Act defines separately, are covered from 11 December 2027.

Reports go through the single reporting platform that ENISA established under Article 16, in close cooperation with the network of national CSIRTs; the European Commission states that the platform has been operational since 11 September 2026. A notification is addressed to the CSIRT of the member state where the manufacturer has its main establishment and, unless circumstances are exceptional, is made available to ENISA at the same time. The point of a single platform is one submission instead of one per authority.

## The three deadlines

*The reporting stages under Article 14, counted from the moment the manufacturer becomes aware*

| Stage | Deadline | Counted from |
| --- | --- | --- |
| Early warning | 24 hours | Becoming aware of the actively exploited vulnerability |
| Notification | 72 hours | Becoming aware |
| Final report | 14 days | A corrective measure being available; for a severe incident, one month after the 72-hour notification |

What each stage must contain is set out in Article 14 of the Regulation and in section 9.1 of the Commission’s guidance on the Act, which the Commission’s reporting page names as the reference. Read both before the first drill rather than during the first incident.

## The four records to have before the clock starts

A report filed in a hurry is only as good as what the team could already prove. Four records decide that.

The reproduction. A finding that cannot be reproduced cannot be described accurately at hour 24 or fixed by day 14. For an application-level vulnerability this is the request that triggers it, the response that shows it and the steps a reviewer can replay. If the finding came from a scanner, insist on this standard at scan time; a pattern that looked risky is an observation, not a finding, and the Act’s reporting duty concerns vulnerabilities that are being exploited, not patterns.

The scope. Which versions, which deployments, which customers. A software bill of materials per release answers the question every notification raises when the vulnerability is in a dependency: which of our products ship the affected component. Without one, the answer at hour 72 is a guess.

The fix evidence. The final report is due no later than 14 days after a corrective measure is available, so the team needs to show the measure corrects the vulnerability: the same reproduction, run again against the fixed version, failing to reproduce. A re-scan that shows a finding closed, with the proof attached, is that evidence in one artefact.

The timeline. Awareness is the trigger, and awareness is a fact about people. When did the first report arrive, who read it, when was it judged to be exploitation rather than a bug, who decided to file. No tool can produce this record after the fact; it is a written process that names an owner, and it is the record most teams find they do not have.

## Where Dokimore helps, and where it stops

Dokimore’s security scanner reports a finding as confirmed only when it can attach the request that triggered it, the response that shows it and a proof of concept a reviewer can replay, inside an evidence bundle with an integrity badge showing it was not edited after the scan. That bundle is the reproduction record. Dependency and SBOM review run beside the dynamic scan, and a re-scan after a fix shows the finding close. Scans run only against targets whose ownership is proven, and exploitation steps need a signed authorisation record.

Where it stops: Dokimore does not file reports, does not decide whether a vulnerability is actively exploited, and does not keep your timeline of awareness. The decision and the written process are yours. For our own product, the coordinated disclosure path is published on our vulnerability disclosure page, which is the other half of being a manufacturer: a way for someone else to tell you.

## What to do this quarter

1. Decide whether you are a manufacturer under the Act for each product you sell into the EU, and write the answer down with the reasoning.
2. Name the person who owns the 24-hour decision and the deputy who owns it when they are asleep.
3. Produce a software bill of materials for the current release of each product and store it where the on-call engineer can read it.
4. Run the drill once: pick a past vulnerability, start the clock, and see which of the four records you could produce in a day.

## Questions people ask

### When did the CRA reporting obligation start?

On 11 September 2026, for manufacturers of products with digital elements. The Act entered into force on 10 December 2024 and its main obligations apply from 11 December 2027; open-source software stewards are covered by the reporting duty from that later date. The obligation is Article 14 of Regulation (EU) 2024/2847.

### What are the CRA reporting deadlines?

Three, all counted from becoming aware of an actively exploited vulnerability: an early warning within 24 hours, a notification within 72 hours, and a final report no later than 14 days after a corrective measure is available. For a severe incident the final report is due within one month of the 72-hour notification. Reports go through the single reporting platform ENISA runs.

### Does every bug have to be reported under the CRA?

No. The reporting duty covers actively exploited vulnerabilities and severe incidents that affect the security of the product. A vulnerability nobody is exploiting falls under the Act’s vulnerability-handling requirements, which apply with its main obligations from 11 December 2027, and a bug that is not a security vulnerability is outside the reporting duty.

### What is the single reporting platform?

A platform established by ENISA under Article 16 of the Act, in close cooperation with the network of national CSIRTs, operational since 11 September 2026 according to the European Commission. A manufacturer submits its notifications through it; each is addressed to the CSIRT of the member state of its main establishment and, unless circumstances are exceptional, made available to ENISA at the same time.

### Can a security scanner produce the report?

It can produce part of the record: the reproduction of the vulnerability, the proof that the fix closed it and the list of affected components, if it keeps evidence per finding and a software bill of materials. It cannot decide that exploitation is happening, name the people who became aware, or file on your behalf. Those belong to a written process with a named owner.

## How we measured this

- The dates, the recipients and the platform are quoted from the European Commission’s two pages on the Act, read on the dates beside the references. The content each stage must carry is in Article 14 of the Regulation and section 9.1 of the Commission’s guidance, which this article names rather than paraphrases. The four records and the quarter’s list are our reading of what an accurate report needs behind it, not guidance from any authority, and this article is not legal advice.
- Dokimore’s behaviour is the product on the article date: confirmed findings carry a request, a response and a replayable proof inside an integrity-badged bundle, dependency and SBOM review run beside the scan, re-scans show a finding close, and the platform files nothing on anyone’s behalf.

## Sources

1. [European Commission, "Cyber Resilience Act: reporting obligations" (page updated 11 September 2026): manufacturers report from 11 September 2026; 24 hours, 72 hours and 14 days; the CSIRT and ENISA; the single reporting platform operational since that date](https://digital-strategy.ec.europa.eu/en/policies/cra-reporting) (read 2026-10-28)
2. [European Commission, "Cyber Resilience Act" (page updated 7 September 2026): Regulation (EU) 2024/2847, in force since 10 December 2024, main obligations from 11 December 2027](https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act) (read 2026-10-28)

Source: https://dokimore.com/blog/cra-vulnerability-reporting-evidence-qa-must-produce
