The Commission moved the CRA standards deadlines again: what it means for app publishers
· 5 min read · CRA news
In short: on 10 November 2026 the Commission adopted decision C(2026) 7861, which pushes back the dates by which the European standards bodies must deliver the CRA's harmonised standards. It changes the timetable for standards, not your obligations as an app publisher.
- The two standards for risk-based design and for vulnerability handling are now due on 30 November 2026, and the product-specific standards on 31 January 2027.
- No CRA harmonised standard is cited in the Official Journal yet, according to a specialist tracker, so no presumption of conformity under Article 27 exists today.
- Most of the CRA's product duties apply from 11 December 2027. Plan to prove conformity yourself, and treat a cited standard as a bonus.
What the Commission decided
The decision amends the Commission's original standardisation request to CEN, CENELEC and ETSI, the one adopted on 3 February 2025 as C(2025) 618. The annex to the new decision, which we read on the Commission's document register, is dated 10 November 2026 and carries these deadlines for adoption by the standards bodies:
| Annex items | What they cover (annex wording, shortened) | Deadline |
|---|---|---|
| 1 | Designing and producing with an appropriate level of cybersecurity based on risks | 30 November 2026 |
| 15 | Vulnerability handling for products with digital elements | 30 November 2026 |
| 16 to 41 | Product-specific (vertical) standards | 31 January 2027 |
| 2 to 14 | Horizontal security requirements, for example no known exploitable vulnerabilities | 30 October 2027 |
Two independent specialist sources describe the change as a further delay of about three months in total: cyberresilienceact.eu in an article of 18 November, and IBF Solutions in a note updated on 16 November. Both link it to a draft published in July that had proposed a shorter two-month move. The CRA Evidence tracker, updated on 17 November, adds that the amendment lapses if one of the standards bodies rejects it within a month of receiving it, in which case the February 2025 dates return. We could not check that clause in the decision itself, because the register only gave us the annex, so treat it as reported.
What this does not change
The deadlines in the request are working dates for the standards bodies. They are not dates for you. Your obligations come from Regulation (EU) 2024/2847, and the Commission's CRA implementation page still lists 11 December 2027 for full application. Reporting of actively exploited vulnerabilities and severe incidents has applied since 11 September 2026, as the same page shows.
The delay matters for one reason: a standard only helps you once it exists and is cited. Under Article 27(1), a product and its processes that conform to harmonised standards whose references are published in the Official Journal are presumed to meet the Annex I requirements those standards cover. Under Article 27(2), the Commission may adopt common specifications by implementing act, but only if standards are missing, were not delivered on time or do not meet the request. The first two EN 40000 parts are already published as European standards, but we have not seen either cited in the Official Journal; our earlier article explains why that distinction matters. The CRA Evidence tracker, as of 17 November, reports that no CRA standard is cited yet.
What it means if you publish an app
Most apps fall in the default category, where you assess conformity yourself. For those, the missing presumption is an inconvenience, not a blocker: you still have to show that you meet Annex I, but nobody can yet tell you that following a particular standard settles the question. Our reading is that the practical effect is more documentation work now, because you cannot point to a cited standard as shorthand. The technical documentation guide shows what to keep.
If your app is an important product in class I, the stakes are higher. Article 32(2) says that where you have not applied, or only partly applied, harmonised standards, common specifications or a suitable certification scheme, or where none exist, you must use EU-type examination followed by internal production control (modules B and C), or full quality assurance (module H). Our reading: without a cited standard, a class I app is steered towards third-party involvement. Class II products already use that route under Article 32(3). You can check where your app sits with the free product class tool.
The delay also affects the market around you. Notified bodies, auditors and tooling vendors cannot finalise their offers without stable standards, which makes early contact with them more useful, not less.
What we would do
- Do not wait for citations. Build your Annex I evidence now, using the Commission guidance and the draft standards as a map, and keep it in your technical file.
- Watch for 30 November 2026, when the vulnerability handling standard is due to be delivered. It is the one the specialist sources expect to be cited first.
- Note the roughly one-month window in which the decision can lapse, and check the Commission's standardisation page for a confirmation.
- If you suspect your app is a class I important product, ask a conformity assessment body about modules B and C or H early.
- Make sure your vulnerability handling process already works, because reporting duties are live. Start with the disclosure policy guide.
Whatever standard is cited later, you will need to know what is inside each app build. Generate an SBOM and check it against known vulnerabilities in seconds.
Open the free scannerSources
- European Commission: annex to Implementing Decision C(2026) 7861 final, 10 November 2026 (PDF, deadlines).
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-Lex: Articles 27 and 32.
- European Commission: CRA implementation fact page (milestones, last updated 27 July 2026).
- cyberresilienceact.eu: the Commission pushed CRA standardisation deadlines back a third month (18 November 2026).
- IBF Solutions: current status of standardisation for the CRA (16 November 2026).
- CRA Evidence: harmonised standards status (updated 17 November 2026; one-month clause, citation status).
This article summarises an EU decision and EU law for practical use. Dates and the one-month clause may change or be clarified. It is not legal advice. Related: CRA timeline for app teams · Does the CRA apply to mobile apps?