The CRA reporting duty is live: what to prepare before you need it
Article 14 of the Cyber Resilience Act applies since 11 September 2026, including to products that were on the market before the main obligations start on 11 December 2027. If you make software or a connected product sold in the EU, it is already your duty.
The short version
You must report actively exploited vulnerabilities in your product and severe incidents that affect its security. There are three steps: an early warning in any event within 24 hours of becoming aware, a notification within 72 hours, and a final report, 14 days after a fix or mitigation is available for a vulnerability, or one month after the notification for an incident. Reports go to the CSIRT of your main establishment and to ENISA through the single reporting platform ENISA runs. The details are in the guide to the reporting obligations.
What you cannot improvise
At 03:00 on a Saturday you will not invent these. Prepare:
- An owner for the process and a stand-in.
- A current SBOM, so you know within minutes which products and versions contain an affected component. See what an SBOM must contain.
- A security contact and a disclosure policy, so reports reach you: generate security.txt and a policy.
- A template for each report, with the facts you will need: the product and versions, the nature of the vulnerability, measures taken, severity and impact.
- A watch of your components, so you learn about exploited vulnerabilities from your SBOM and not from a customer.
Small makers
Micro and small enterprises are not fined for missing the 24-hour deadline of the early warning; they must still submit it and meet the other deadlines and duties. Open-source stewards have lighter duties. Check the Regulation and the guidance for your situation.
Information only, not legal advice. The classifier shows whether your product is likely in scope.
More from the blog
- Look up a Brazilian company by CNPJ without scraping
- A first KYB check in one call: what to ask, what to keep
- Live SSL, domain and vulnerability badges for your README
- Check an npm or PyPI package for known vulnerabilities before you install
- All tools and prices
- Guides
Data and prices change; every API response states its source and date. Informational only, not financial, legal or tax advice.