CRA support period: how long, and what to publish
As of 6 October 2026, the Cyber Resilience Act (Regulation (EU) 2024/2847) makes the manufacturer set a support period that reflects how long the product is expected to be in use, and that is at least five years unless the product is expected to be used for less (Article 13(8)). During it the manufacturer must handle vulnerabilities effectively and provide security updates. The obligation applies from 11 December 2027, and the support period must be stated clearly to users.
The rules in short
| Topic | What the Regulation says | Source |
|---|---|---|
| Length | Reflects the expected time in use; at least five years, unless the product is expected to be used for a shorter time, then that time | Article 13(8) |
| What counts | Reasonable user expectations, nature and intended purpose of the product, relevant Union law on lifetime | Article 13(8) |
| Duty during the period | Handle vulnerabilities effectively in line with Annex I, Part II | Article 13(8) |
| Updates stay available | Each security update stays available for at least ten years after issue or for the rest of the support period, whichever is longer | Article 13(9) |
| Tell users | Specify the support period clearly at the time of purchase, and give its end date, at least the month and year, in the user information and, where technically feasible, notify users when support ends | Article 13(19); Annex II point 7 |
| Document it | The reasoning belongs in the technical documentation | Annex VII |
What to do
- List what you ship and, for each product, the expected period of use. A library used inside long-lived devices has a different answer from a short-lived app.
- Set the support period in years or as an end date, never below five years unless you can justify a shorter expected use time in writing.
- Publish the end date where users see it: product page, README and the information that accompanies the product (Annex II).
- Keep every security update downloadable for at least ten years, or for the rest of the support period if that is longer (Article 13(9)). Do not delete old release assets.
- Record how you chose the period. A short note per product is enough.
- Check which other duties apply with the classifier, and keep a contact point and policy live during the whole period.
Open-source stewards are not manufacturers and are not bound by Article 13; see the open-source guide.
Article references
Article 13(8), 13(9) and 13(19); Annex I, Part II; Annex II; Annex VII; Articles 69 and 71.
This is general information, not legal advice. It does not say that any product is compliant or certified.
Free tools
- Product classifier: Is your product in scope, and in which category?
- SBOM checker: Check a CycloneDX or SPDX file in your browser.
- security.txt and disclosure policy: The contact file and policy the Regulation expects.
- Repository check: what a GitHub repository already shows.
Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.