Shipmark / Free tools / Substantial modification check

Is this app update a substantial modification under the CRA?

For one release of one app, about two minutes. Nothing you answer leaves your browser.

Why it matters: an app first released in the EU before 11 December 2027 only has to meet the CRA requirements if it is substantially modified from that date (Article 69(2)). Reporting exploited vulnerabilities applies to it either way (Article 69(3)). For an app released later, a substantial modification means the new version is assessed again. Apps get updated often, so the question comes back with every release.

Answer for the release you are about to ship. The check follows the four questions of the Commission guidance of July 2026 and writes a short record of your answers to keep with the risk assessment.

The release
1. When was this app first offered to users in the EU?
2. Is this release a new variant of the app?

A separate build that differs in its components, configuration or enabled features, such as a white-label copy for another client or a "Pro" edition. Summaries of the guidance say variants are distinct products, each with its own placing date (point 14).

3. Since 11 December 2027, was an earlier release of this app already treated as a substantial modification?
4. What does the release mainly do?
5. Is there a cybersecurity risk assessment for the version before this one?

The four questions below compare the release with the attack scenarios that assessment identified. See how to write one for an app.

6. Does the release introduce new threat vectors?

New interfaces, communication channels, execution environments or external dependencies. For an app: a new SDK that talks to its own servers, a new API or backend, a new deep link or intent handler, a WebView that loads remote content, Bluetooth or NFC.

7. Does it enable attack scenarios that the risk assessment did not consider?

For example storing login tokens to keep users signed in, sharing data with another app, or a new payment flow. A feature that the assessment already anticipated does not count.

8. Does it change how likely an attack scenario already identified becomes?

For example removing or weakening a check, opening a feature that was internal to all users, or lowering a minimum OS version.

9. Does it change the potential impact of those scenarios?

For example the app now stores or processes more sensitive data (health, location, payment details), asks for new permissions or controls a device.

What the rules say

RuleWhat it means for an app
Dates Article 71(2)The regulation applies from 11 December 2027. Article 14 (reporting) applies from 11 September 2026, and Chapter IV (notified bodies) from 11 June 2026.
Apps already on the market Article 69(2)Products placed on the market before 11 December 2027 are subject to the requirements of the regulation only if, from that date, they undergo a substantial modification.
Reporting for all Article 69(3)By way of derogation, the reporting obligations of Article 14 apply to all products in scope placed on the market before 11 December 2027. An older app still reports actively exploited vulnerabilities and severe incidents within 24 hours, 72 hours and the final report deadline.
Software versions Guidance, points 13 to 15As summarised by Schutzwerk and CRA Experts: all copies of a software version are placed on the market when that version is first offered, later downloads are only making it available, and an update that is not a substantial modification does not change that date.
The four questions Guidance, points 107, 110 and 111As summarised by CVD Portal, Turingpoint and CRA Experts: does the update introduce new threat vectors, enable new attack scenarios, change the likelihood of scenarios already identified, or change their impact? Four negative answers, with the risk assessment's assumptions and mitigations still valid, likely mean the change is not substantial. The scale or complexity of the change does not decide.
Security updates Guidance, points 108 and 109As summarised by CVD Portal and Turingpoint: a security update is not a substantial modification even with significant technical changes, as long as it does not change the intended purpose or bring new or increased risks, for example a new external dependency.
After a substantial modification Guidance, points 116 and 133As summarised by CVD Portal, Turingpoint and CRA Experts: the modified product is treated as a new product (point 116), the obligations concern the modified parts unless the change affects the cybersecurity of the product as a whole, and the support period is re-derived rather than automatically reset (point 133).

How to use this in an agency

If the result is that the CRA requirements apply, the next steps are the Annex I checklist, the support period of the new version, the technical documentation and the EU declaration of conformity.

Shipmark keeps an SBOM of every release of every client app, so you can see which components a release added or changed before you answer question 6. Founding agencies use it free until 1 April 2027.

Join the free beta

Sources

We read Articles 69 and 71 directly. The guidance point numbers come from the summaries listed above; read the guidance itself before relying on a point. The check runs in your browser and does not send or store your answers. It gives a general orientation and is not legal advice: a substantial modification is decided case by case by the manufacturer. Related: Does the CRA apply? · Risk assessment guide · Support period calculator