EU Cyber Resilience Act: Vulnerability Reporting, SBOMs and Support Periods for Software Makers

ApexlyTech Team 11 min read
EU Cyber Resilience Act: Vulnerability Reporting, SBOMs and Support Periods for Software Makers

TL;DR: The EU Cyber Resilience Act (CRA, Regulation (EU) 2024/2847) entered into force on 10 December 2024, and its reporting obligations in Article 14 have applied since 11 September 2026. If you make software or connected products sold in the EU, you must now notify any actively exploited vulnerability and any severe incident affecting your product's security: an early warning within 24 hours, a fuller notification within 72 hours and a final report later. Reports go through ENISA's Single Reporting Platform to the national CSIRT acting as coordinator. Reporting applies even to products placed on the market before the main rules start. Everything else, including secure-by-design requirements, a software bill of materials (SBOM), a support period of at least five years and a coordinated vulnerability disclosure policy, applies from 11 December 2027. The Digital Omnibus proposal of November 2025 would change how incidents are reported across EU laws, but it does not amend the CRA and had not been adopted when we checked.

The dates that matter

DateWhat applies
10 Dec 2024The CRA enters into force
11 Jun 2026Chapter IV: rules for notifying conformity assessment bodies
11 Sep 2026Article 14: reporting of actively exploited vulnerabilities and severe incidents
11 Dec 2027All other obligations, including the essential cybersecurity requirements, SBOM, support periods and CE marking

The source is Article 71(2) of the Regulation: "This Regulation shall apply from 11 December 2027. However, Article 14 shall apply from 11 September 2026 and Chapter IV (Articles 35 to 51) shall apply from 11 June 2026." Reporting did start on schedule: ENISA launched the Single Reporting Platform on 11 September 2026, stating that from that day manufacturers are required to report actively exploited vulnerabilities and severe incidents.

Does it apply to you?

The CRA covers "products with digital elements" made available on the EU market: hardware and software products, including software sold on its own, together with their remote data processing solutions. A few points decide most cases for software companies.

  • Installed and downloadable software is in scope. Desktop and mobile apps, firmware, libraries sold commercially, and the software inside connected devices.
  • Pure SaaS is generally outside the CRA. Recital 12 says the NIS2 Directive applies to cloud services and service models such as Software as a Service. But a backend is in scope as a "remote data processing solution" when the product could not perform one of its functions without it (Article 3(2) and recital 11). The API your mobile app or device depends on is part of the product.
  • Non-monetised open source is outside. Recital 18 says free and open-source software that is not monetised by its manufacturer should not be considered a commercial activity. Foundations and similar bodies that steadily support open-source projects intended for commercial use are "open-source software stewards" with a lighter regime (Article 24), and they cannot be fined.
  • Some sectors have their own rules. Medical devices, vehicles, aviation and marine equipment that already fall under specific EU legislation are excluded or partly excluded.
  • Some products carry extra conformity requirements. Annex III lists "important" products (classes I and II), such as identity management systems, browsers, password managers, VPNs, operating systems and routers; Annex IV lists "critical" ones. Commission Implementing Regulation (EU) 2025/2392 of 28 November 2025 gives the technical description of each category.

Location does not matter. A manufacturer in Pakistan, the Gulf or the US selling into the EU is covered, and the reporting rules have a fallback order for deciding which Member State's CSIRT receives your reports when you have no EU establishment (Article 14(7)).

Reporting: what, when and where

Two kinds of event

Article 14 covers two separate things:

  • An actively exploited vulnerability in your product: one where there is reliable evidence that a malicious actor has exploited it in a system without the owner's permission. A vulnerability you found internally and nobody has exploited is not reportable under Article 14 (although it still falls under your vulnerability handling duties from December 2027).
  • A severe incident having an impact on the security of your product: one that negatively affects, or is capable of negatively affecting, the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions, or that has led or is capable of leading to the introduction or execution of malicious code in the product or in users' systems (Article 14(5)). A compromise of your build pipeline or update server is the textbook example.

The deadlines

StageActively exploited vulnerabilitySevere incident
Early warningWithin 24 hours of becoming aware, with the Member States where the product is made available, if knownWithin 24 hours, including whether the incident is suspected to be caused by unlawful or malicious acts
NotificationWithin 72 hours: the product, the general nature of the exploit and of the vulnerability, corrective or mitigating measures taken and those users can take, and how sensitive the information isWithin 72 hours: the nature of the incident, an initial assessment, corrective measures taken and those users can take
Final reportNo later than 14 days after a corrective or mitigating measure is available: description, severity and impact, information on any malicious actor, details of the security updateWithin one month after the 72-hour notification: detailed description, severity and impact, the likely root cause, mitigations applied and ongoing

Two details catch people out. The 24-hour clock starts when you become aware, not when you have finished investigating, so the early warning is meant to be short and provisional. And where necessary, the CSIRT can ask for an intermediate report on status updates. Micro and small enterprises cannot be fined for missing the 24-hour early-warning deadline (Article 64(10)(a)), but they still have to report.

Where reports go

Notifications are submitted once, through ENISA's Single Reporting Platform, and are received simultaneously by ENISA and by the CSIRT designated as coordinator in the Member State of your main establishment in the EU: where decisions on the cybersecurity of your products are predominantly taken. ENISA has deployed the platform in an "initial operating capability" and has continued to release updates since launch. A delegated regulation adopted under the CRA, Delegated Regulation (EU) 2026/881, sets out when a CSIRT may delay passing a notification on to others on cybersecurity grounds.

Telling your users

After becoming aware of an actively exploited vulnerability or a severe incident, you must also inform the impacted users, and where appropriate all users, about it and about any risk mitigation and corrective measures they can take, where appropriate in a structured, machine-readable format that is easy to process automatically (Article 14(8)). If you do not do so in time, the CSIRT may.

Products already on the market

Article 69(3) makes Article 14 apply to all products with digital elements that fall within the CRA's scope and were placed on the market before 11 December 2027. In other words, the products you are selling today are already subject to reporting, even though the design and documentation requirements do not apply to them until December 2027.

What the Digital Omnibus would change, and what it would not

On 19 November 2025 the Commission proposed a "Digital Omnibus" (COM(2025) 837) to simplify the EU's data, privacy and cybersecurity rules. Among other things, it proposes a single entry point for incident reports under several laws, built on the CRA's Single Reporting Platform, so that one notification could satisfy more than one reporting regime. Its explanatory memorandum states that it leaves the underlying incident reporting requirements unchanged, and it does not amend the CRA's deadlines. At the end of October 2026 the proposal was still in the legislative process, with no adopted text. Plan for the CRA as written.

What applies from 11 December 2027

Secure by design and vulnerability handling

Annex I sets the essential requirements in two parts. Part I covers the product: no known exploitable vulnerabilities at release, a secure-by-default configuration, protection against unauthorised access, data minimisation, confidentiality and integrity of data, resilience, a limited attack surface, security logging, and the ability to deliver security updates, automatically by default where appropriate. Part II covers your processes, including:

  • An SBOM. "Drawing up a software bill of materials in a commonly used and machine-readable format covering at the very least the top-level dependencies of the products" (Annex I, Part II(1)).
  • Fixing vulnerabilities without delay, through security updates provided free of charge and, where technically feasible, separately from functionality updates.
  • Testing and review of the product's security, regularly.
  • Public disclosure of fixed vulnerabilities once an update is available, with a description, the affected products, the impact and severity, and remediation guidance.
  • A coordinated vulnerability disclosure policy, put in place and enforced, plus a contact address for reporting vulnerabilities.
  • Secure distribution of updates.

The SBOM is for authorities, not necessarily the public

The SBOM forms part of your technical documentation. You must provide it to a market surveillance authority on a reasoned request (Annex VII), and you may choose to share it with users (Annex II). The Commission may specify the SBOM's format and elements by implementing act (Article 13(24)). Until it does, the two established machine-readable formats are SPDX and CycloneDX. Generate the SBOM in your build pipeline from the lock files you ship, so it always matches the release, rather than maintaining it by hand.

Support periods

You must define a support period during which vulnerabilities are handled. It "shall be at least five years", unless the product is expected to be in use for less than five years, in which case it matches the expected use time (Article 13(8)). Each security update must remain available for at least ten years after it is issued, or for the rest of the support period if that is longer (Article 13(9)). The end date of support, at least the month and year, must be clear at the time of purchase (Article 13(19)), and it is part of the information you give users under Annex II.

A single point of contact

Manufacturers must designate a single point of contact so users can communicate directly and rapidly with them, including to report vulnerabilities, and must not limit those means to automated tools (Article 13(17)).

Third-party components

When you find a vulnerability in a component, including an open-source one, you must report it to the person or entity that maintains it, and share the fix with them if you made one (Article 13(6)). This turns "upstream it when you can" into an obligation.

Penalties

Breaching the essential requirements or the obligations in Articles 13 and 14 can cost up to EUR 15 million or 2.5 percent of worldwide annual turnover, whichever is higher. Other listed obligations carry up to EUR 10 million or 2 percent, and supplying incorrect, incomplete or misleading information to authorities up to EUR 5 million or 1 percent (Article 64).

What a software vendor should do now

  1. Map your products. List what you sell or distribute in the EU, decide which are products with digital elements, which backends are part of them, and whether any are Annex III or IV categories.
  2. Write the reporting runbook. Who decides that a vulnerability is "actively exploited"? Who drafts and submits the 24-hour early warning, out of hours? Rehearse it with a tabletop exercise, and keep a short template for each of the three stages.
  3. Register for the Single Reporting Platform and confirm which Member State's CSIRT is your coordinator, based on where your product security decisions are taken.
  4. Watch for exploitation signals. Subscribe to threat intelligence relevant to your stack, including the vulnerability databases and known-exploited lists, and connect them to your incident process.
  5. Prepare user notifications: a security advisory page, an email or in-app channel, and ideally a machine-readable advisory format such as CSAF.
  6. Generate SBOMs in CI for every release, in SPDX or CycloneDX, stored alongside the build.
  7. Decide support periods for each product line, at least five years for most software, and make sure your release and branching strategy can deliver security fixes separately from features for that long.
  8. Publish a coordinated vulnerability disclosure policy and a security contact. A security.txt file (RFC 9116) on your website is a simple way to make the contact findable.
  9. Close Annex I gaps before December 2027. Secure defaults, update mechanisms, logging and threat modelling all take engineering time. Start with the products you will still be selling in 2028.

Our earlier guide to industrial IoT architecture and security covers device identity and over-the-air updates in more detail.

How ApexlyTech can help

We build and maintain web, mobile, cloud and IoT products, and we can help you set up the engineering side of CRA readiness: SBOM generation in CI, a secure update path, security logging, and the internal tooling for a vulnerability and incident runbook. See our custom software, IoT solutions and cloud solutions services, or contact us. Confirm the legal position for your products with qualified counsel; this guide is not legal advice.

Frequently asked questions

When did CRA vulnerability reporting start?

On 11 September 2026. Since then, manufacturers must report actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform, including for products placed on the market before December 2027.

What are the CRA reporting deadlines?

An early warning within 24 hours of becoming aware, a notification within 72 hours, and a final report within 14 days after a fix is available for a vulnerability, or within one month after the notification for a severe incident.

Does the CRA apply to SaaS?

Standalone SaaS is generally covered by the NIS2 Directive rather than the CRA. A backend without which a product could not perform one of its functions, such as the API behind a mobile app or device, is in scope as a remote data processing solution.

Do I have to publish my SBOM?

No. You must draw it up and provide it to market surveillance authorities on request. Sharing it with users is optional.

How long must I support my software?

For at least five years, unless the product is expected to be in use for less time. Each security update must stay available for at least ten years after release or for the rest of the support period, whichever is longer.

Did the Digital Omnibus delay the CRA?

No. The November 2025 Digital Omnibus proposal would create a single entry point for incident reports across several EU laws, but it does not amend the CRA's deadlines, and it had not been adopted at the end of October 2026.

Sources