Support period

How long must a CRA support period be, and does a substantial modification extend it?

5 worked examples from Commission guidance C(2026) 5252 final, reproduced word for word.

Also asked

  • Is the CRA support period five years by default?
  • Do I have to patch old versions of my software under the CRA?
  • Does a substantial modification reset the CRA support period?
  • What counts as an additional cost when upgrading under Article 13(10)?
  • How do I justify the support period I declared?

Article 13(8) sets the support period by reference to the time the product is expected to be in use. The five year figure is a safeguard floor rather than a default, and products expected to last longer need correspondingly longer periods. Article 13(10) lets a manufacturer remediate only the version last placed on the market, provided users can upgrade free of charge and without additional costs. A substantial modification triggers a reassessment but does not automatically reset or extend the period.

The other Annex I Part II requirements continue for every version. Article 13(10) relieves remediation, not coordinated vulnerability disclosure or information sharing.

Key takeaways

  1. Article 13(8) requires manufacturers to determine and state the support period during which vulnerability handling and security updates are provided.
  2. The support period must reflect the reasonably expected product lifetime based on user expectations, hardware durability, and industry norms.
  3. The support period date or duration must be clearly stated on packaging, digital labels, or point-of-sale materials prior to purchase.
  4. Security updates must be provided free of charge throughout the entire declared support period.

At a glance

Legal basis
Article 13(8) and (10), recital 60
Five years
A safeguard floor, not the default (point 126)
Criteria
Reasonable user expectations, nature of the product, Union law on product lifetimes
Not an additional cost
Personnel time, testing, configuration, dependency upgrades (point 130)
Is an additional cost
New hardware, infrastructure replacement, fundamental environment changes

Last reviewed 27 July 2026

Verified against The Annex to Commission Communication C(2026) 5252 final of 27 July 2026, and Regulation (EU) 2024/2847 as published in OJ L, 20.11.2024, read at EUR-Lex on 27 July 2026

Five years is a floor, and reading it as a default is the common error

Article 13(8) sets the support period based on the expected use time of the product. Manufacturers evaluate reasonable user expectations, the nature of the product, intended purpose, and relevant Union product lifetime rules.[2]

Point 126 of the guidance clarifies that the five-year minimum is a safety floor, not a default. Products expected to remain in use longer require longer support periods. An industrial controller used for ten years cannot use a five-year support period simply because five years meets the minimum.

Article 13(8) lists additional factors to document in the technical file: support periods of similar market products, operating environment availability, third-party component lifecycles, and ADCO guidance under Article 52(15). Manufacturers must evaluate these factors proportionately.

CRA referenceArticle 13(8), recital 60

Article 13(10) relief for software that ships every few months

Examples 52 and 53 apply Article 13(10) relief to frequently updated software, such as smartphone operating systems and enterprise applications. Manufacturers may remediate vulnerabilities only in the latest release if users can upgrade free of charge without additional costs.

Point 130 defines additional costs narrowly. Routine testing, configuration adjustments, and dependency maintenance count as standard operational effort. Mandatory hardware purchases or forced infrastructure replacements count as additional costs and void the relief.

Each substantially modified version still requires a declared support period under Article 13(8). Other Annex I Part II duties continue, including CVD policies and information sharing. Manufacturers should inform users who have not upgraded when technically feasible under Article 13(19).

CRA referenceArticle 13(10) and (19), Annex I, Part II

A substantial modification reopens the question without answering it

Points 133 to 135 require reassessing support periods against Article 13(8) criteria after a substantial modification. Examples 54 to 56 illustrate different outcomes.

Adding features or cleaning modes to consumer appliances does not change the support period if hardware durability and user expectations stay the same. Cloud backend updates that do not alter physical lifetime also leave the support period unchanged.

Replacing core computing platforms with longer-lived components does alter the period. When hardware upgrades extend expected user operation, the manufacturer must recalculate and declare a longer support period.[1]

CRA referenceArticle 13(8), Article 3, point (30)

The Commission’s examples, word for word

5 examples, reproduced exactly as published. Each carries the section, guidance point and page it comes from. The bold line above each quotation is our summary of the outcome and is not part of the source.

Example 52

Section 5 Support period, point 131, page 45

Article 13(10) relief. Remediate the latest OS version only, where upgrades are free and need no new hardware

A manufacturer places a smartphone model on the EU market and declares a support period of X years from the date of placement on the market, during which it will provide security updates addressing vulnerabilities. During that period, the manufacturer releases regular software updates and substantially modified versions of the operating system, which users can install free of charge without requiring new hardware.

The manufacturer may, in accordance with Article 13(10), address and remediate vulnerabilities for the latest version of the operating system made available for that smartphone model, provided that earlier versions can be upgraded free of charge and without additional costs. For the duration of the support period, the manufacturer remains subject to the other vulnerability handling requirements, such as coordinated vulnerability disclosure and information-sharing measures.

Example 53

Section 5 Support period, point 131, page 45

Article 13(10) relief for iterative enterprise software. Testing and configuration effort is not an additional cost

A manufacturer places an enterprise software product with digital elements on the market and releases substantially modified versions every few months, reflecting security improvements, new features and compatibility with updated operating systems and platforms. Each version is placed on the market with a declared support period in accordance with Article 13(8). The manufacturer expects users to upgrade regularly as part of normal operation and provides access to the latest version free of charge. Applying upgrades may require reasonable operational effort, such as testing or configuration adjustments, but does not require additional costs, such as the purchase of new hardware or fundamental infrastructure changes. In this context, the manufacturer may rely on Article 13(10) to discontinue addressing and remediating vulnerabilities for earlier versions once users can upgrade to the latest version, while continuing to comply with the other vulnerability-handling requirements for all subsequent substantially modified versions.

Example 54

Section 5.1 Substantial modifications and the support period, point 134, page 46

Support period unchanged. New cleaning modes do not alter hardware durability or user expectations

A manufacturer places on the market a robot vacuum cleaner with an expected use time of X years, determined on the basis of the nature of the product with digital elements, including the physical durability and wear characteristics of the hardware components, and taking into account reasonable user expectations as to that product's lifetime. The manufacturer sets a support period of X years. After Y years, the manufacturer releases a software update that qualifies as a substantial modification, adding new cleaning modes and navigation features. The software update does not affect the physical durability of the hardware and does not alter reasonable user expectations as to that product's lifetime. The Article 13(8) criteria therefore continue to indicate the same expected use time. The support period of the modified product with digital elements aligns with the remaining expected use time as originally determined.

New in the adopted text. It has no counterpart in the earlier consultation draft.

Example 55

Section 5.1 Substantial modifications and the support period, point 134, page 46

Support period unchanged. Rearchitecting the cloud back end does not change the nature of the machinery

A manufacturer places on the market a complex industrial machinery product with digital elements, with a cloud back-end that constitutes a remote data processing solution. The expected use time is X years, determined in light of reasonable user expectations and the nature of the product with digital elements, such as the physical durability of the machinery hardware and expected wear and tear. The support period is set to align with that expected use time at X years. After Y years, the manufacturer rearchitects the cloud back-end (the remote data processing solution), introducing new APIs and data flows, in a manner that qualifies as a substantial modification of the product with digital elements but does not alter the nature of that product or affect user expectations. The Article 13(8) criteria therefore continue to indicate the same expected use time. The support period of the modified product with digital elements aligns with the remaining expected use time as originally determined.

New in the adopted text. It has no counterpart in the earlier consultation draft.

Example 56

Section 5.1 Substantial modifications and the support period, point 135, page 47

Support period recalculated upwards. A new computing platform changes the expected use time

A manufacturer places on the market a programmable logic controller (PLC) with an expected use time of X years, determined primarily on the basis of the nature of the product with digital elements and the durability of the underlying hardware. The support period is set accordingly. Several years after the initial placing on the market, the manufacturer carries out a substantial modification consisting of the replacement of the PLC's embedded computing platform, including the processor, memory and runtime environment, with a new generation of components designed for a significantly longer operational lifetime. As a result of the modification, reasonable user expectations and the nature of the product with digital elements change: the PLC's user may now reasonably expect the PLC to remain in productive use beyond its originally declared expected use time, supported by the new computing platform. The Article 13(8) criteria therefore indicate a longer expected use time, and the manufacturer recalculates the support period for that specific PLC accordingly.

New in the adopted text. It has no counterpart in the earlier consultation draft.

Sources

Every claim above traces to one of these. Items marked Binding are law in force. Everything else is interpretive and is labelled as such.

  1. [1]

    European Commission · Section 5 and 5.1, points 125 to 135 · C(2026) 5252 final · Final, adopted 27 July 2026

    Article 26 guidance sets out the Commission's interpretation of the CRA. It does not bind economic operators, and only the Court of Justice of the European Union can give an authoritative interpretation of the Regulation.

    Accessed 2026-07-27

  2. [2]

    European Union · Article 13(8) · CELEX:32024R2847

    Without prejudice to the second subparagraph, the support period shall be at least five years.

    Accessed 2026-07-27

  3. [3]

    European Union · Article 13(10) and (19) · CELEX:32024R2847

    Accessed 2026-07-27

  4. [4]

    European Union · Recital 60 · CELEX:32024R2847

    Accessed 2026-07-27

Further reading on this site

This worked example is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Turn the guidance into an audit-ready file

Free CRA classification for your product, a vulnerability disclosure portal on your own domain, and Article 14 deadline tracking. Receiving and tracking reports is free for every manufacturer placing products with digital elements on the EU market.