Two dates matter for app teams: 11 September 2026 (reporting, already running) and 11 December 2027 (everything else).
- The Cyber Resilience Act (CRA) entered into force on 10 December 2024 and applies in full from 11 December 2027 (Article 71).
- Article 14, the duty to report actively exploited vulnerabilities and severe incidents, has applied since 11 September 2026, and it covers apps that are already on the market (Article 69(3)).
- An app placed on the market before 11 December 2027 is otherwise in scope only if it is substantially modified from that date (Article 69(2)).
- As of 16 November 2026, about thirteen months remain before the main obligations apply.
The timeline at a glance
| Date | What happened or applies | Why an app team cares |
|---|---|---|
| 23 October 2024 | Parliament and Council adopt Regulation (EU) 2024/2847. | The text is fixed. |
| 20 November 2024 | Published in the Official Journal. | Starts the clock for entry into force. |
| 10 December 2024 | Entry into force, on the twentieth day after publication (Article 71(1)). | No obligations for manufacturers yet. |
| 11 June 2026 | Chapter IV, Articles 35 to 51, applies. It covers the notification of conformity assessment bodies. | Mostly relevant if your app is an important or critical product and needs a third party. |
| 27 July 2026 | The Commission publishes non-binding guidance, C(2026) 5252. | The best available reading of scope, support periods and substantial modification. |
| 11 September 2026 | Article 14 applies: reporting of actively exploited vulnerabilities and severe incidents. ENISA's Single Reporting Platform launches the same day. | You must be able to report today, also for old apps. |
| 11 December 2027 | The Regulation applies in full (Article 71(2)). | Annex I requirements, vulnerability handling, technical documentation, EU declaration of conformity and CE marking apply to apps placed on the market from this date. |
| 11 June 2028 | Certificates issued under other EU cybersecurity harmonisation legislation stay valid until this date, unless they expire earlier (Article 69(1)). | Rarely relevant for apps. |
2024: adoption and entry into force
The CRA, Regulation (EU) 2024/2847, is dated 23 October 2024 and was published in the Official Journal on 20 November 2024. Under Article 71(1) it entered into force on the twentieth day after publication, which is 10 December 2024. Entry into force did not create duties for manufacturers. It started the transition period that ends with Article 71(2).
11 June 2026: notified bodies
Article 71(2) brings Chapter IV (Articles 35 to 51) forward to 11 June 2026. This chapter sets up how Member States designate and notify the conformity assessment bodies that will be needed for certain products. Most apps can be assessed by the manufacturer itself, so this date rarely changes your work. It matters if your app turns out to be an important product, such as a password manager or a VPN, because that can bring a third-party assessment into play. See the scope guide for how Annex III products are treated.
27 July 2026: the Commission guidance
On 27 July 2026 the Commission published its guidance on the application of the CRA as C(2026) 5252. The Commission describes it as non-binding. It covers scope, including remote data processing solutions and free and open-source software, what counts as a substantial modification, how support periods should be understood, and how to meet the reporting obligations. It is not a legal deadline, but it is the document most useful when you decide whether a specific app is covered.
11 September 2026: reporting started
Article 71(2) says Article 14 applies from 11 September 2026. ENISA launched the CRA Single Reporting Platform the same day. Under Article 14, for an actively exploited vulnerability the manufacturer sends:
- an early warning "without undue delay and in any event within 24 hours" of becoming aware of it;
- a vulnerability notification within 72 hours of becoming aware;
- a final report no later than 14 days after a corrective or mitigating measure is available.
For a severe incident, the early warning is also due within 24 hours and the notification within 72 hours, and the final report is due within one month after the incident notification (Article 14(4)).
The part that surprises many teams is Article 69(3): the exception to the grandfathering rule says Article 14 applies to all in-scope products with digital elements, including those placed on the market before 11 December 2027. An app you shipped in 2019 and have not touched since is still covered by the reporting duty, and the trigger is your becoming aware of an actively exploited vulnerability, not the age of the app. Details are in CRA vulnerability reporting for app teams, and the free reporting deadlines tool turns your awareness time into the three dates.
11 December 2027: full application
Article 71(2) states that the Regulation applies from 11 December 2027. From that date, an app placed on the market must meet the essential cybersecurity requirements, have its conformity assessed, carry technical documentation and an EU declaration of conformity, and bear the CE marking. The guides below cover each part in turn:
- Annex I requirements as concrete checks for a mobile app
- the cybersecurity risk assessment
- the support period
- technical documentation
- a coordinated vulnerability disclosure policy
Apps already on the market before 11 December 2027
Article 69(2) provides that products placed on the market before 11 December 2027 are subject to the Regulation only if, from that date, they undergo a substantial modification. Article 69(3) removes the reporting duty from that rule, as described above. In practice an existing app is outside the Annex I, conformity assessment and CE marking requirements while it stays unmodified, but a release after that date that amounts to a substantial modification can pull the app into scope. The free release check helps you assess a specific update. Whether a given change is substantial depends on the facts and on the Commission guidance, so keep a record of your reasoning.
After 2027
Article 69(1) keeps certain certificates and approval decisions issued under other EU harmonisation legislation valid until 11 June 2028, unless they expire earlier or that legislation says otherwise. This rarely concerns an app team, but it is the next date in the Regulation's own transition rules.
A practical plan by date
- Now: make sure you can report. Register for the Single Reporting Platform, name who decides that a vulnerability is actively exploited, and keep a list of the apps and versions you maintain.
- During 2027: run a risk assessment per app, decide the support period you will declare, and build the technical file as you go rather than at the end.
- Before 11 December 2027: check each release in the weeks around that date for substantial modification, and have the declaration of conformity and CE marking approach settled for new apps.
Try it on your own app: the free Shipmark scanner builds a CycloneDX SBOM from a lockfile in the browser and checks it against OSV.dev. Not sure the CRA applies? Use the six-question CRA check.
Sources
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: adoption date and date of entry into force from the document metadata.
- Article 71, Entry into force and application, OJ L 2024/2847, 20.11.2024.
- Article 69, Transitional provisions.
- Article 14, Reporting obligations of manufacturers.
- European Commission: guidance to support the implementation of the CRA, C(2026) 5252, 27 July 2026.
- ENISA: The CRA Single Reporting Platform is launched, 11 September 2026.
- DataGuard: the CRA timeline, used to cross-check the dates.
This guide summarises EU law and non-binding Commission guidance for practical use. It is not legal advice. Related: Does the CRA apply to mobile apps? · CRA vulnerability reporting · Support period · Technical documentation.
Originally published on shipmark.eu, where the guide is kept up to date. More guides for app teams: shipmark.eu/guides.
Top comments (0)