How long must you provide security updates under the CRA?
Last verified: 2026-11-21.
Information, not legal advice. Our reading of the official sources, not reviewed by a lawyer. You decide how the CRA applies to your product; for an opinion you can rely on, ask a lawyer; for a third-party conformity assessment, a notified body. This guide helps you work with the EU Cyber Resilience Act (Regulation (EU) 2024/2847) but does not certify, assess or guarantee the compliance of any product. You remain responsible for your product's conformity assessment, CE marking and reporting. Last verified against official sources: 2026-11-21.
Short answer
- You set a support period for each product: the time during which you make sure that vulnerabilities of the product, including its components, are handled effectively and in line with Annex I Part II (CRA Art. 13(8), first subparagraph).
- The support period reflects how long the product is expected to be in use and is at least five years. Only where the product is expected to be in use for less than five years does it match that shorter expected use time (CRA Art. 13(8), second and third subparagraphs).
- Five years is a minimum, not a default. Products expected to be used for longer should get longer support periods (CRA Recital 60; Guidance, point 126).
- Each security update made available during the support period must stay available for at least 10 years after it is issued or for the rest of the support period, whichever is longer (CRA Art. 13(9)).
- You state the end date of the support period, at least the month and year, at the time of purchase (CRA Art. 13(19)).
How to set the support period
Article 13(8) says what you take into account: in particular, reasonable user expectations, the nature of the product including its intended purpose, and Union law that determines the lifetime of products with digital elements. You may also consider the support periods of products with similar functionality from other manufacturers, the availability of the operating environment, the support periods of integrated third-party components that provide core functions, and guidance from the CRA administrative cooperation group (ADCO) and the Commission. These matters are weighed in a manner that ensures proportionality (CRA Art. 13(8), second subparagraph).
Recital 60 gives examples. Hardware components such as motherboards or microprocessors, network devices such as routers, modems or switches, and software such as operating systems or video-editing tools are often in use for longer than five years, and products for industrial settings often for much longer. A shorter period can fit a contact-tracing application intended for use during a pandemic, or subscription software that becomes unavailable to the user once the subscription expires (CRA Recital 60).
Put the information you used to determine the support period in the technical documentation (CRA Art. 13(8), fifth subparagraph; Annex VII point 4). Market surveillance authorities monitor how manufacturers apply these criteria, ADCO is to publish indicative support periods for product categories, and the Commission may set minimum support periods for specific categories by delegated act (CRA Art. 13(8), fourth subparagraph; Art. 52(16)).
What you do during the support period
- Address and remediate vulnerabilities without delay, including by providing security updates, separately from functionality updates where technically feasible (CRA Annex I Part II point 2).
- Disseminate available security updates without delay and free of charge, with advisory messages, unless you agreed otherwise with a business user for a tailor-made product (CRA Annex I Part II point 8).
- Keep the technical documentation up to date, at least during the support period (CRA Art. 31(2)), and take corrective measures if you learn that the product or your processes do not meet Annex I (CRA Art. 13(21)).
Reporting under Article 14 does not stop at the end of the support period. In the Commission's reading, the reporting obligations continue after a product is no longer supported, while the vulnerability handling obligations last for the support period (Guidance, point 210).
Software released in versions
In the Commission's reading, each substantially modified version of a software product placed on the market needs its own declared support period that meets Article 13(8), including the five-year minimum unless that version's expected use time is demonstrably shorter (Guidance, point 128). For software, you may remediate vulnerabilities only in the version you last placed on the market, provided users of earlier versions can move to it free of charge and without additional costs to adjust the hardware and software environment in which they use the original version (CRA Art. 13(10); Guidance, points 129–131). A substantial modification does not automatically reset the support period; you recalculate it only if the modification changes the factors that set the expected use time (Guidance, points 133–135).
What you tell users
- The end date of the support period, at least month and year, clearly and understandably at the time of purchase and, where applicable, on the product, its packaging or by digital means (CRA Art. 13(19), first subparagraph).
- In the information and instructions for users, the type of technical security support you offer and the end date of the support period (CRA Annex II point 7).
- Where technically feasible, a notification that the product has reached the end of its support period (CRA Art. 13(19), second subparagraph).
These rules apply to products placed on the market from 11 December 2027, and to earlier products only if they are substantially modified from that date (CRA Art. 69(2), 71(2)).
To check this for your product with an AI assistant, add Shieldbook to Claude or connect the Shieldbook MCP server (https://shieldbook.ppftec.com/mcp); the scope check is also at https://shieldbook.ppftec.com/check.
FAQ
Is a five-year support period always enough?
No. Five years is the minimum where the product is expected to be in use for five years or more. If the product is reasonably expected to be in use for longer, the support period should be longer (CRA Art. 13(8); Commission CRA FAQ 4.5.2; Guidance, point 126).
Can units still be sold after the support period ends?
In the Commission's reading, units already placed on the market may still be made available after their support period expires, but new units you place on the market need a support period set under Article 13(8) (Commission CRA FAQ 4.5.3).
Must security updates be free of charge?
Yes, unless you and a business user agreed otherwise for a tailor-made product (CRA Annex I Part II point 8). The CRA does not require you to provide security updates free of charge for earlier versions that users can upgrade from at no additional cost (Guidance, footnote 19).
Sources
Opened by the compliance analyst; dates are when each source was last read.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), OJ L, 20.11.2024. Citation URL: https://eur-lex.europa.eu/eli/reg/2024/2847/oj/eng. File read (authentic OJ PDF via the Publications Office): https://publications.europa.eu/resource/cellar/21b7d4eb-a6e2-11ef-85f0-01aa75ed71a1.0006.01/DOC_1. Recitals 59–62, Art. 13, 31, 52, 69 and 71 and Annexes I, II and VII read 2026-11-21.
- European Commission, Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act), Communication C/2026/6013, OJ C, 17.11.2026, not binding (point 8). Citation URL: https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=OJ:C_202606013. File read: https://publications.europa.eu/resource/cellar/dcbc848b-e227-11f1-aefc-01aa75ed71a1.0006.01/DOC_1. Points 8, 121–136 with footnotes 17–21 and points 209–224 read 2026-11-21.
- European Commission, Cyber Resilience Act implementation: frequently asked questions, version 1.4, last update 4 September 2026, entries 4.5.1–4.5.3. Landing page: https://digital-strategy.ec.europa.eu/en/library/cyber-resilience-act-implementation-frequently-asked-questions. File read (Markdown version): https://ec.europa.eu/newsroom/dae/redirection/document/123307 (2026-11-21).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.