Substantial modification: when does an update make a new product?
7 min read
Software changes all the time. Under the Cyber Resilience Act, whether an update legally places a new product on the market determines who counts as the manufacturer, whether a new conformity assessment is needed and whether older products fall under the Regulation. This guide summarises what the Regulation, the Commission guidelines of July 2026 and the Commission FAQ say about it.
What the Cyber Resilience Act means by a substantial modification
A substantial modification is a change to the product after it has been placed on the market which affects its compliance with the essential cybersecurity requirements in Annex I, Part I, or which results in a modification to the intended purpose for which the product has been assessed (Art. 3(30)).
Recital 39 is more specific for software: an update is a substantial modification if it changes the intended purpose and the manufacturer did not foresee this in its initial risk assessment – or if the nature of the hazard has changed or the cybersecurity risk has increased. According to the recital, adding new functions typically leads to a larger attack surface. Whether a functionality change comes on its own or together with a security update makes no difference.
Source: Art. 3(30) CRA · Recital 39 CRA
When the classification matters
The Commission names four cases in which the classification is decisive:
- An importer or distributor substantially modifies a product – it is then considered the manufacturer (Art. 21).
- Someone else substantially modifies a product and makes it available on the market – they too are considered the manufacturer (Art. 22).
- A product placed on the market before 11 December 2027 is substantially modified after that date – only then do the requirements of the Cyber Resilience Act apply to it (Art. 69(2)).
- For products from 11 December 2027: does a new version need a new conformity assessment? With software and its many versions, this is the question that comes up most often.
Versions without a substantial modification need no new conformity assessment and do not change the date of placing on the market. The Commission illustrates this with an example: version 1.0.0 is released on 1 January 2028, a bug fix 1.0.1 on 15 January – both are considered placed on the market on 1 January.
Source: Art. 21 CRA · Art. 22 CRA · Art. 69(2) CRA · Commission guidance C/2026/6013, points 15, 91
The Commission's four questions
The guidelines set out questions for software updates. The Commission stresses that it remains a case-by-case assessment and that the list is not exhaustive. In essence, the following should be asked for every update:
- Does it introduce new threat vectors – additional interfaces, communication channels, execution environments or external dependencies?
- Does it enable new attack scenarios, i.e. new ways of unauthorised access, manipulation or misuse of the product or its data?
- Does it change the likelihood of known attack scenarios – for example because less effort is needed, untrusted actors gain easier access or safeguards are weakened?
- Does it change the impact of known attack scenarios – more affected data or functions, more severe consequences, poorer detection or recovery?
If the answer is no four times and the assumptions of the risk assessment remain valid, the update is likely not a substantial modification. Otherwise the manufacturer should reassess the risks and check whether the essential requirements are still met.
Important: the yardstick is not the size of the change but its effect on the risk. The Commission's example is a small 'remember me' feature that stores authentication tokens locally. It introduces new risks such as token theft and session hijacking – and is therefore a substantial modification. The same goes for an inconspicuous diagnostics export that stores operational data unencrypted.
Source: Commission guidance C/2026/6013, points 107, 110–112, Examples 44, 45
Security updates
A security update designed to decrease the risk that does not modify the intended purpose is not a substantial modification. This applies even if it modifies functions or performance – as long as that is solely for the purpose of reducing the risk. Minor functionality updates such as visual enhancements, new languages or new pictograms are generally not considered substantial either.
The guidelines go one step further: this holds even for significant technical changes, for example tightening firewall rules, disabling unused ports or making an already available multi-factor authentication mandatory.
The limit: if a security update changes the purpose or introduces new risks, it can still be a substantial modification. The Commission's example: after a vulnerability, an encryption mechanism is switched to an external key management service operated by a third party. New external interfaces, altered data flows, a new dependency – substantial, even though the trigger was security.
Source: Recital 39 CRA · Commission guidance C/2026/6013, points 108, 109, Examples 46–50
Planned functions in the risk assessment
Functions that the manufacturer has already anticipated, assessed and mitigated in its risk assessment do not trigger a substantial modification later. The Commission cites a messaging app whose risk assessment already covers group chats, and a monitoring system with control features that are initially disabled but whose risks and safeguards were assessed from the start.
Conversely, new functions that change the purpose of the product as a whole are as a rule substantial. The Commission's example: a dashboard that previously only displayed machine data can suddenly control and restart machines.
It therefore pays to describe and mitigate foreseeable developments in the risk assessment from the outset.
Source: Commission guidance C/2026/6013, points 105, 106, Examples 40–43
Consequences of a substantial modification
- The modified product is considered newly placed on the market. The original manufacturer remains the manufacturer.
- Conformity must be verified and, where appropriate, reassessed. Where a notified body is involved, a change that could amount to a substantial modification should be reported to it.
- Documentation and tests for parts not affected by the change may be reused. The conformity assessment – including that of a notified body – should focus on the modified parts.
- A new version may need a new EU declaration of conformity, especially when it implements a substantial modification.
- The support period does not automatically restart. It is only recalculated if the change affects the factors on which the expected use time was based.
Regardless of how an update is classified: the risk assessment and technical documentation must be kept up to date continuously, and vulnerability handling under Annex I, Part II continues in any case.
Source: Recital 41 CRA · Commission guidance C/2026/6013, points 113, 116, 122, 123, 132–135 · Commission FAQ on the CRA, 6.8
When someone else modifies the product
Anyone who substantially modifies someone else's product and makes it available on the market becomes the manufacturer. Their obligations under Articles 13 and 14 apply to the part affected by the modification – or to the entire product if the modification has an impact on its cybersecurity as a whole. For the unchanged parts, the original manufacturer remains responsible.
This must be distinguished from integration: anyone who assembles components – even modified ones – into a new product of their own is not modifying someone else's product but placing their own on the market, and is the manufacturer of the whole.
Source: Art. 21 CRA · Art. 22(1), (2) CRA · Commission guidance C/2026/6013, points 117–121, Example 51
Products already on the market before December 2027
Products placed on the market before 11 December 2027 are subject to the requirements of the Cyber Resilience Act only if they are substantially modified after that date. The reporting obligations under Article 14 nevertheless apply to them – since 11 September 2026.
The Commission FAQ explains this with a TV placed on the market in mid-2027: a bug fix in 2028 changes nothing. An update in 2029 that lets the TV control smart home systems is a substantial modification.
Even then the manufacturer does not have to bring the entire legacy product into compliance, only the modified parts – unless the modification negatively affects the cybersecurity of the product as a whole.
Source: Art. 69(2), (3) CRA · Art. 71(2) CRA · Commission FAQ on the CRA, 1.4 · Commission guidance C/2026/6013, point 124
In practice
- Go through the four questions before every release and record the answer with a short justification – including a 'not substantial'.
- Describe and mitigate planned functions in the risk assessment up front instead of reassessing them later.
- Ship security updates separately from functionality updates where possible – that also makes the classification easier.
- Look closely at new external interfaces, third-party services or altered data flows, even if the update 'only' serves security.
- Update the risk assessment and technical documentation with every release, however the classification turns out.
The Commission guidelines are not binding; the decision in the individual case remains with the manufacturer. This guide does not replace legal advice.
Related guides
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 3(30), Art. 21, 22, 69, Recitals 39–41 (EUR-Lex, Official Journal)
- Commission guidance C/2026/6013, OJ C, 17 Nov 2026, Sections 2.1, 4 and 5.1 (non-binding)
- Commission FAQ on the Cyber Resilience Act, version 1.4 of 4 September 2026
Status of the Commission guidance: the Commission approved its content on 27 July 2026 (C(2026) 5252). On 17 November 2026 the guidance was published in the Official Journal as Communication C/2026/6013, in all official languages. According to our comparison, the point numbers have not changed. The guidance is not binding, but it shows how the Commission reads the Regulation (as of 11/2026).
First published 30 Oct 2026, last updated 30 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.