CRA deadlines 2026–2027: what applies when, and what to do before each date
Last verified: 2026-11-13.
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-13.
Short answer
- Already in force today (13 November 2026): the CRA entered into force on 10 December 2024, the rules on notifying conformity assessment bodies apply since 11 June 2026, and manufacturers' reporting of actively exploited vulnerabilities and severe incidents applies since 11 September 2026 (CRA Art. 71(1)–(2); Commission CRA page).
- From 11 December 2027 the rest of the Regulation applies: security requirements, vulnerability handling, technical documentation, conformity assessment, EU declaration of conformity and CE marking (CRA Art. 71(2)).
- Products placed on the market before 11 December 2027 must meet those requirements only if they are substantially modified from that date, but reporting under Article 14 applies to them already (CRA Art. 69(2)–(3)).
Key terms
- Entry into force and application are different. The CRA entered into force on the twentieth day after its publication in the Official Journal (published 20 November 2024), but most of it applies only from 11 December 2027 (CRA Art. 71).
- Placing on the market: the first making available of a product with digital elements on the Union market (CRA Art. 3(21)).
- Making available on the market: supplying a product for distribution or use on the Union market in the course of a commercial activity, paid or free (CRA Art. 3(22)).
- Substantial modification: a change after placing on the market that affects compliance with the Annex I Part I requirements or modifies the intended purpose for which the product was assessed (CRA Art. 3(30)).
- Notified body: a conformity assessment body designated under the CRA and notified to the Commission and the other Member States (CRA Art. 3(29), 35(1)).
- Support period: the time during which you must handle the product's vulnerabilities under Annex I Part II (CRA Art. 3(20)).
The dates at a glance
| Date | What applies or happens | Who it concerns | Article |
|---|
| 20 Nov 2024 | Regulation (EU) 2024/2847 published in the Official Journal | Everyone (for information) | OJ L, 20.11.2024 |
| 10 Dec 2024 | Entry into force. No manufacturer duty applies yet | Everyone (for information) | Art. 71(1); Commission CRA page |
| 11 Dec 2025 | Deadline for the Commission to adopt an implementing act with the technical description of the important (Class I and II) and critical product categories. Whether it was adopted: unverified, not checked on 2026-11-13 | Commission; relevant for your product class | Art. 7(4) |
| 11 Jun 2026 | Chapter IV (Articles 35 to 51) applies: notifying authorities, requirements for and notification of conformity assessment bodies | Member States, conformity assessment bodies | Art. 71(2); Recital 126 |
| 11 Sep 2026 | Article 14 applies: reporting of actively exploited vulnerabilities and severe incidents through ENISA's Single Reporting Platform | Manufacturers, including for products placed on the market before 11 Dec 2027 | Art. 14, 69(3), 71(2) |
| 11 Dec 2026 | Member States "shall strive to ensure" there are enough notified bodies in the Union by this date. A target for Member States, not a duty for you | Member States | Art. 35(2) |
| 11 Dec 2027 | The rest of the Regulation applies, including Article 13, Annex I, Articles 28, 30, 31 and 32. Reporting duties of open-source software stewards also start | Manufacturers, importers, distributors, open-source software stewards | Art. 71(2); Commission reporting page |
| 11 Jun 2028 | Last day of validity for EU type-examination certificates and approval decisions on cybersecurity requirements issued under other Union harmonisation legislation, unless they expire earlier or that legislation says otherwise | Makers of products also covered by other EU product law | Art. 69(1) |
| 11 Sep 2028 | Commission report on the effectiveness of the Single Reporting Platform | Commission | Art. 70(2) |
| 11 Dec 2030 | First Commission evaluation report, then every four years | Commission | Art. 70(1) |
Now: reporting has applied since 11 September 2026
If you make a product in scope, you have had to report since 11 September 2026. Article 14 requires an early warning within 24 hours of becoming aware of an actively exploited vulnerability, a notification within 72 hours, and a final report no later than 14 days after a corrective or mitigating measure is available (CRA Art. 14(1)–(2)); severe incidents have their own three steps, explained in our reporting guide. You submit through ENISA's Single Reporting Platform, operational since 11 September 2026 (Commission reporting page).
This applies to products you placed on the market years ago, too: Article 69(3) makes Article 14 apply to all in-scope products placed on the market before 11 December 2027 (CRA Art. 69(3)).
What a small team should have in place today:
- A named person who submits reports, and a backup.
- A personal EU Login account with multi-factor authentication for that person. ENISA advises registering on the platform itself only when you need to submit a notification; registration then takes a few minutes (ENISA SRP FAQ, updated 15 Oct 2026).
- A first-hour routine: who confirms exploitation, who drafts the early warning, and which coordinator CSIRT receives it.
- A list of the products you have placed on the market, so you know what is covered.
The platform is in English only for now (ENISA SRP FAQ). Non-compliance with Article 14 can be fined up to EUR 15 million or 2.5% of total worldwide annual turnover, whichever is higher, under rules set by each Member State (CRA Art. 64(1)–(2)). Full walk-through of the three reports: CRA vulnerability reporting.
Before 11 December 2027: get each new release ready
From 11 December 2027, every product you place on the market must meet the essential requirements and come with the paperwork. The work takes time, so plan backwards from your release dates, not from the deadline.
| By when (our suggestion) | Do this | Article |
|---|
| Early 2027 | Decide, per product, whether the CRA likely applies, your role and the product's class (default, important Class I or II, critical) | Art. 2, 3, 7, 8; Annexes III–IV |
| Early 2027 | If a product is important Class I, check whether you can apply harmonised standards, common specifications or a certification scheme in full; if not, plan a notified-body route (module B + C, or module H) | Art. 32(1)–(2) |
| Mid 2027 | Write the cybersecurity risk assessment and set the support period (at least five years unless the product is expected to be used for less) | Art. 13(2)–(3), 13(8) |
| Mid 2027 | Put vulnerability handling in place: an SBOM, a coordinated vulnerability disclosure policy, and security updates kept available for at least 10 years after issue or the rest of the support period if longer | Art. 13(8)–(9); Annex I Part II(1) |
| Before release | Draw up the technical documentation before placing the product on the market, and keep it updated at least during the support period | Art. 13(12), 31(1)–(2) |
| Before release | Complete the conformity assessment, draw up the EU declaration of conformity and affix the CE marking (for software: on the declaration or on the accompanying website) | Art. 13(12), 30(1), 30(3), 32(1) |
| Before release | Prepare the Annex II user information, your contact details, a single point of contact, and the support end date (at least month and year) shown at purchase | Art. 13(16)–(19) |
| After release | Keep the technical documentation and declaration for at least 10 years, or the support period if longer | Art. 13(13) |
If you may need a notified body, start early. Chapter IV has applied since 11 June 2026, so Member States can notify bodies, and they should "strive to ensure" enough of them by 11 December 2026 (CRA Art. 35(2), 71(2)). Whether enough bodies will be available for your product category and timing is not something the Regulation settles. The item-by-item list is in our CRA checklist for small teams.
Products already on the market before 11 December 2027
Article 69(2) says products placed on the market before 11 December 2027 are subject to the CRA requirements only if, from that date, they undergo a substantial modification (CRA Art. 69(2)). Two practical consequences:
- Reporting still applies to these products (CRA Art. 69(3)).
- Substantial modification is a test, not a version-number rule: a change counts if it affects compliance with Annex I Part I or modifies the intended purpose (CRA Art. 3(30)).
For software shipped as frequent releases, whether a given release is a new placing on the market or a modification of an existing product is an interpretation question. Needs professional review: "Under Articles 3(21), 3(30) and 69(2), does release X of our product, first made available on date Y, have to meet the CRA requirements from 11 December 2027?"
If your product is also covered by other EU product law and holds an EU type-examination certificate or approval decision on cybersecurity requirements under that law, Article 69(1) keeps it valid until 11 June 2028, unless it expires earlier or that legislation provides otherwise (CRA Art. 69(1)).
What may still change
- Standards. On 10 November 2026 the Commission amended its standardisation request to extend the delivery deadline for all vertical standards and some horizontal standards by three months (Commission standardisation page, last update 12 Nov 2026). This moves deadlines for standardisation bodies, not the CRA's application dates. The page does not list any harmonised standard cited in the Official Journal; we did not search the Official Journal itself.
- Digital Omnibus. The Commission published the Digital Omnibus proposal (COM(2025) 837) on 19 November 2025 (Commission). On 13 November 2026 the Parliament's Legislative Observatory showed procedure 2025/0360(COD) awaiting a committee decision, not adopted, and its list of amended acts did not include the CRA (Legislative Observatory). We found no adopted act changing the CRA dates in the sources we opened.
- Health data. We understand that Regulation (EU) 2025/327 (European Health Data Space) amends some CRA provisions for electronic health record systems from 26 March 2027; unverified, we have not read the amending text.
- Next re-check of this guide: 2027-01-04.
How Shieldbook helps
Shieldbook is a set of templates and tools to help you prepare for the EU Cyber Resilience Act (Regulation (EU) 2024/2847). For these dates it gives a reporting runbook for the 24-hour, 72-hour, 14-day and 1-month steps, a scope and product-class decision tree, a support-period statement, a technical documentation skeleton and a 30-day plan for a team of one to five people. Each template cites the article it supports. You review and submit reports yourself on ENISA's Single Reporting Platform.
Start with the free 5-question scope checker for a provisional indication: https://shieldbook.ppftec.com/check. See the kit: https://shieldbook.ppftec.com/.
FAQ
Which CRA obligations apply right now?
Since 11 September 2026, manufacturers must report actively exploited vulnerabilities and severe incidents under Article 14, including for products placed on the market earlier (CRA Art. 14, 69(3), 71(2)). Most other obligations apply from 11 December 2027.
Did the CRA apply from 10 December 2024?
It entered into force then, but entry into force is not application. Manufacturers had no CRA duty until Article 14 started on 11 September 2026 (CRA Art. 71(1)–(2)).
What changed on 11 June 2026?
Chapter IV started to apply: the rules for notifying authorities and for conformity assessment bodies that want to become notified bodies (CRA Art. 35–51, 71(2)). It creates no new duty for manufacturers, but it is the start of notified-body capacity for products that need one.
Has the 11 December 2027 date been postponed?
Not in the sources we opened on 13 November 2026. The Commission's CRA page still gives 11 December 2027 (Commission CRA page), the November 2026 change concerns standardisation deadlines (Commission standardisation page), and the Digital Omnibus proposal was not adopted (Legislative Observatory).
Do products I sold before December 2027 need CE marking?
Not unless they are substantially modified from 11 December 2027 (CRA Art. 69(2)). Reporting under Article 14 still applies to them (CRA Art. 69(3)).
When do open-source software stewards have to report?
From 11 December 2027, according to the Commission and ENISA (Commission reporting page; ENISA SRP FAQ).
How long must I keep my CRA documents?
At least 10 years after placing the product on the market, or for the support period if longer (CRA Art. 13(13)).
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. Recital 126, Art. 1–8, 13, 14(1)–(2), 28(3)–(5), 29–31, 32(1)–(3), 33(5), 35–39, 61–71 and Annex I Part I read 2026-11-13.
- European Commission, Cyber Resilience Act page, last update 7 September 2026: https://digital-strategy.ec.europa.eu/en/policies/cyber-resilience-act (2026-11-13).
- European Commission, CRA reporting obligations page, last update 11 September 2026: https://digital-strategy.ec.europa.eu/en/policies/cra-reporting (2026-11-13).
- European Commission, CRA standardisation page, last update 12 November 2026: https://digital-strategy.ec.europa.eu/en/policies/cra-standardisation (2026-11-13).
- ENISA, Single Reporting Platform FAQ, updated 15 October 2026: https://www.enisa.europa.eu/topics/product-security/single-reporting-platform-srp/frequently-asked-questions (2026-11-13).
- European Parliament, Legislative Observatory, procedure 2025/0360(COD) (Digital Omnibus): https://oeil.europarl.europa.eu/oeil/en/procedure-file?reference=2025/0360(COD) (2026-11-13).
- European Commission, news of 19 November 2025 on the digital omnibus, last update 24 August 2026: https://digital-strategy.ec.europa.eu/en/news/simpler-eu-digital-rules-and-new-digital-wallets-save-billions-businesses-and-boost-innovation (2026-11-13).
The Shieldbook kit: templates and worked examples
This site needs JavaScript for the scope checker and the waitlist form.