By DataTip · Published
TL;DR: CRA reporting duties may apply to products sold years ago, but age alone does not determine whether a product is covered. Manufacturers should assess the product's scope, which entity marketed it under its name or trademark in the EU, and whether an actively exploited vulnerability or severe incident affects or could affect product security.
- The source says CRA reporting requirements may reach products sold years ago; age alone does not establish whether a product is covered.
- The CRA can cover software, hardware, separately placed components, firmware and certain remote data processing solutions, subject to stated exclusions and conditions.
- An importer or distributor may become the manufacturer for CRA purposes by marketing a product under its own name or trademark, or by substantially modifying it.
- An actively exploited vulnerability requires reliable evidence of malicious exploitation without the system owner's permission; good-faith testing and coordinated disclosure without malicious intent do not trigger that duty.
- A compromised development, production or maintenance environment – including a build pipeline or security-update channel – may create a severe incident even without demonstrated customer harm.
A product can leave your current catalogue and still deserve a review of its CRA reporting duties. The EU Cyber Resilience Act’s reporting requirements took effect on September 11, 2026, and may apply to products sold years earlier. That does not mean every older product is covered. It means age alone is not a sound reason to leave a product line without an accountable owner for vulnerability and incident response.
CRA reporting duties may apply to products sold years ago, but age alone does not determine whether a product is covered. Manufacturers should assess the product’s scope, which entity marketed it under its name or trademark in the EU, and whether an actively exploited vulnerability or severe incident affects or could affect product security.
For manufacturers and product leaders, start with three questions: Was the product placed on the EU market? Does it fall within the CRA’s definition of a product with digital elements? Which entity marketed it under its name or trademark? The answers help identify legacy lines that merit closer assessment, without deciding the legal status of any particular product. The reporting requirements also precede the broader product-compliance regime, which the source says does not apply until December 11, 2027. Fisher Phillips describes the reporting requirements and their potential reach to older products.
Why might CRA reporting duties apply to older products?
The CRA reporting requirements concern actively exploited vulnerabilities and severe incidents affecting products with digital elements. The source says they may apply even to products a company sold years ago – not that every product remains covered simply because it once entered the market. Product age is a reason to investigate, not a determination of coverage.
That distinction matters for discontinued lines. A review focused only on current launches could overlook older connected software, hardware or components that were placed on the EU market. Nor does the supplied guidance say that retirement or discontinuation, by itself, settles whether reporting duties apply. The practical question is whether the product and responsible entity fit the conditions described below.
What products fall within the CRA’s scope?
The CRA covers products with digital elements: software and hardware products, certain remote data processing solutions, and software or hardware components placed on the market separately. The named examples span industrial controllers, connected consumer devices, operating systems, mobile applications, network equipment and firmware. For a legacy product, the relevant boundary may therefore include more than the finished device or application.

The source lists several exclusions: medical devices and in vitro diagnostics; type-approved motor vehicles; certified civil aviation equipment; and marine equipment. It also excludes products developed or modified exclusively for national security or defense, products designed to process classified information, and spare parts manufactured to the same specifications as the parts they replace.
Standalone software-as-a-service is generally outside the CRA. A SaaS service may be captured as a remote data processing solution when the manufacturer designs and develops that remote processing and the product cannot perform its functions without it. So a product’s dependence on a cloud service is relevant, but does not by itself establish that the service falls within the CRA. The source notes that when the cloud service is the product itself, NIS2 or DORA might be relevant instead.
Who carries the reporting duty for a legacy product?
Manufacturers carry the reporting duty for covered products placed on the EU market. The source defines a manufacturer as a natural or legal person that develops or manufactures a product with digital elements – or has it designed, developed or manufactured – and markets it under its own name or trademark. The product does not need to be made in the EU; placement on the EU market is the relevant connection.
This means checking who made an older product is not enough. A US company that sells into the EU through a distributor is treated as a manufacturer under the source’s account and must report. Manufacturers established outside the EU must also designate an authorized representative in the EU. For legacy lines, the name or trademark under which the product was marketed can help clarify which entity bears responsibility.
Importers and distributors do not file the reports themselves under the source’s account, but they have related obligations. They must inform the manufacturer without undue delay when they become aware of a product vulnerability. If the product presents a significant cybersecurity risk, they must immediately inform the market-surveillance authorities in the Member States where they made it available.
An importer or distributor becomes the manufacturer for CRA purposes if it markets a product under its own name or trademark, or substantially modifies a product already on the market. Private-label and white-label arrangements therefore deserve careful review; the commercial label alone may not make the role clear. Open-source software stewards follow a separate, lighter regime. The European Commission’s stated position, as reported in the source, is that their reporting obligations begin on December 11, 2027, not September 2026.
Which legacy product events can trigger CRA reporting?
The source identifies two triggers: an actively exploited vulnerability and a severe incident that affects, or is capable of affecting, product security. These are distinct categories. A weakness being found or disclosed is not automatically the same as malicious exploitation, and a severe incident does not require confirmed customer harm.

An actively exploited vulnerability requires reliable evidence that a malicious actor exploited it in a system without the system owner’s permission. Good-faith security testing and coordinated disclosure without malicious intent do not trigger this vulnerability-reporting duty. When assessing a legacy product, distinguish evidence of malicious exploitation from a finding or disclosure that lacks that element.
A severe incident is one that negatively affects, or could negatively affect, the product’s ability to protect the availability, authenticity, integrity or confidentiality of data or functions. The definition also covers an incident that has led, or could lead, to malicious code being introduced or executed in the product or in a user’s network and information systems.
The incident need not originate in a customer’s environment. A compromise of the manufacturer’s own development, production or maintenance environment may qualify if it could increase cybersecurity risk for users. The source gives malicious code injected into a build pipeline or security-update channel as examples. Customer harm does not need to have occurred: being capable of negatively affecting product security is enough under the source’s description. A team that looks only for unauthorized acquisition of customer data – the focus of many US breach-notification standards – could miss an incident that warrants CRA assessment.
Make the legacy-product review a responsibility decision
The source supports a focused review, not a blanket conclusion about discontinued products. Identify older products with digital elements that were placed on the EU market; establish which entity marketed each under its name or trademark; and consider whether separately placed components or qualifying remote processing form part of the product. Then determine which product lines need an accountable owner able to assess vulnerabilities and incidents against the CRA’s trigger categories.
Keep the two regulatory dates distinct: reporting requirements took effect on September 11, 2026, while the broader product-compliance regime does not apply until December 11, 2027. That difference is a reason not to defer every legacy-product question until the later regime. It is not, by itself, a conclusion that any particular older product is covered.
Key takeaways
- The source says CRA reporting requirements may reach products sold years ago; age alone does not establish whether a product is covered.
- The CRA can cover software, hardware, separately placed components, firmware and certain remote data processing solutions, subject to stated exclusions and conditions.
- An importer or distributor may become the manufacturer for CRA purposes by marketing a product under its own name or trademark, or by substantially modifying it.
- An actively exploited vulnerability requires reliable evidence of malicious exploitation without the system owner’s permission; good-faith testing and coordinated disclosure without malicious intent do not trigger that duty.
- A compromised development, production or maintenance environment – including a build pipeline or security-update channel – may create a severe incident even without demonstrated customer harm.
Practical tips
- For older products, establish where they were marketed in the EU and which entity and brand were associated with them.
- Clarify whether a product depends on separately marketed components or remote processing to perform its functions.
- Review private-label and white-label arrangements alongside actual marketing and modification practices.
Related Posts
14. November 2026
CRA Vendor Notifications: What Software Buyers Should Require
A supplier's legal reporting clock does not answer the buyer's question: who…
12. November 2026
Autonomous AI Agents: Which Actions Still Require Human Sign-Off?
A TCS study highlights the gap between expected AI productivity and…
10. November 2026
EU E-Invoicing Mandates: Which Country Rules Shape Your Roadmap?
Does your invoicing roadmap start with ViDA in 2030? It may need to account for…




