What does Commission guidance C(2026) 5252 clarify on the Cyber Resilience Act?
Commission guidance C(2026) 5252, adopted on 27 July 2026 under Article 26(1) of Regulation (EU) 2024/2847, sets out the European Commission’s interpretive view on Cyber Resilience Act scope, remote data processing solutions, open-source commercial activity, the four-factor substantial modification test, support periods, and Class I self-assessment. Only the Regulation is legally binding.
Last updated 17 November 2026
Key takeaways
- The European Commission adopted C(2026) 5252 on 27 July 2026 under Article 26(1) of Regulation (EU) 2024/2847 across 84 pages, 67 numbered examples, and 5 remote data processing use cases.
- Regulation (EU) 2024/2847 is legally binding, whereas C(2026) 5252 is interpretive guidance that market surveillance authorities and notified bodies use as their working reference.
- Point 110 sets a four-factor test for substantial modification based on threat vectors, attack scenarios, likelihood, and impact rather than code diff size.
- Point 126 confirms that five years is a minimum floor rather than a default support period, and point 133 confirms that a substantial modification requires re-deriving rather than resetting the support clock.
Binding law versus interpretive guidance
Article 26(1) of Regulation (EU) 2024/2847 requires the European Commission to publish guidance assisting economic operators in applying the EU Cyber Resilience Act. On 27 July 2026 the Commission adopted Commission guidance on the application of Regulation (EU) 2024/2847 (Cyber Resilience Act) under document reference C(2026) 5252.
On 17 November 2026 the Official Journal of the European Union published the guidance in the 24 official languages as Communication C/2026/6013. The Official Journal text keeps all 67 numbered examples. Cite C/2026/6013 in a technical file, because it is the published version.
Point 8 of the communication states the legal boundary clearly. C(2026) 5252 creates no new legal obligations and binds no economic operator. Only the articles and annexes of Regulation (EU) 2024/2847 carry binding legal force, and only the Court of Justice of the European Union gives authoritative interpretations of Union law. In practice, national market surveillance authorities, notifying authorities, and notified bodies treat C(2026) 5252 as their working reference when reviewing technical files.
Topic summary comparing Regulation text and C(2026) 5252
Each row separates the binding provision in Regulation (EU) 2024/2847 from the interpretive reading in C(2026) 5252 and links to the verbatim worked examples.
| Topic | Binding rule (Regulation (EU) 2024/2847) | Interpretive view (C(2026) 5252) | Worked examples |
|---|---|---|---|
| Software scope and web applications | Article 2(1), Article 3(1)Applies to hardware and software products with digital elements placed on the EU market whose use includes a direct or indirect data connection. | Locally installed mobile and desktop apps are in scope. Browser-only web apps and informational websites stay out unless they act as remote data processing for an in-scope product. | Product scope examples → |
| Remote data processing solutions | Article 3(1), Article 3(2)Remote data processing designed by or under the responsibility of the manufacturer is part of the product when its absence prevents a product function. | Self-hosted or cloud APIs that a client app calls for core functions belong to the product. Back-end systems behind that interface that the product never contacts directly fall outside. | Remote data processing examples → |
| Free and open-source software | Recital 18, Article 3(23), Article 24Open-source software supplied outside a commercial activity is excluded. Open-source software stewards carry light-touch duties under Article 24. | Monetising paid editions or gating releases and security fixes behind donations makes supply commercial. Pull-request contributors without release control carry zero CRA obligations. | Open-source examples → |
| Substantial modification | Article 3(30), Articles 21 and 22A post-market change that affects Annex I Part I compliance or alters the assessed intended purpose counts as a new placing on the market. | Points 107 to 111 set a four-factor risk test covering threat vectors, attack scenarios, likelihood, and impact. Security updates that add new external dependencies lose the security carve-out. | Substantial modification examples → |
| Support period and iterative releases | Article 13(8), Article 13(10)The support period must reflect expected product use time and run at least five years unless expected use time is shorter. Article 13(10) allows single-version patching under conditions. | Point 126 clarifies that five years is a minimum safeguard rather than a default. Point 133 confirms that substantial modifications trigger re-assessment rather than an automatic clock reset. | Support period examples → |
| Repairs, spare parts, and integration | Article 2(6), Article 13Spare parts made available exclusively to replace identical components in existing products under identical specifications are exempt. | Pre-CRA components can be integrated when the whole-product risk assessment clears them. Assembling off-the-shelf modules with custom firmware creates a new product rather than a modification. | Repairs and spare parts examples → |
| Product classification and conformity routes | Articles 7, 8, and 32, Annexes III and IVAnnex III Class I products can self-assess under Module A only when harmonised standards, common specifications, or a qualifying certification scheme are applied. | Points 147 to 155 state that a harmonised standard must cover all risks of the core functionality and be applied in full to preserve Module A eligibility across the product. | Classification examples → |
| Cybersecurity risk assessment | Article 13(2), Annex I Part IManufacturers must perform and document a cybersecurity risk assessment and apply its results across design, development, production, delivery, and maintenance. | Manufacturers can treat certain risks through documented intended-environment constraints or host operating-system controls rather than duplicating controls inside the product. | Risk assessment examples → |
Software scope and remote data processing
Binding rule: Article 2(1) and Article 3(1) cover hardware and software products with digital elements, including remote data processing solutions designed under the manufacturer’s responsibility whose absence prevents a product function.
Interpretive reading in C(2026) 5252: Mobile apps installed from app stores and desktop apps packaged with web technologies for local installation are products in scope. Pure browser-delivered SaaS and informational websites remain outside the CRA unless they provide remote data processing for an installed client or connected device. In multi-tier back ends, only the interface the product communicates with directly counts as a remote data processing solution, while internal downstream ledgers that the client never addresses stay out.
Free and open-source software and stewards
Binding rule: Open-source software developed and supplied outside a commercial activity falls outside manufacturer obligations, while Article 24 creates specific cybersecurity policy and cooperation duties for open-source software stewards.
Interpretive reading in C(2026) 5252: Twenty-two worked examples map the commercial boundary. Charging for a commercial edition or gating software releases and security patches behind financial contributions turns supply into a commercial activity. Accepting unconditional donations or selling independent consulting services around freely available code leaves the project non-commercial. Individual contributors who submit pull requests without release authority carry no CRA duties.
The four-factor test for substantial modification
Binding rule: Under Article 3(30), any change after placing on the market that affects Annex I Part I compliance or modifies the assessed intended purpose treats the modified product as newly placed on the market.
Interpretive reading in C(2026) 5252: Points 107 to 111 replace code-size guesswork with four risk questions: whether the change adds threat vectors, enables new attack scenarios, raises the likelihood of known scenarios, or increases their impact relative to the documented risk assessment. Point 108 confirms that risk-reducing security updates remain outside substantial modification unless, under point 109, they alter product boundaries, change data flows, or introduce external third-party service dependencies.
Support periods and iterative software releases
Binding rule: Article 13(8) ties the support period to expected use time with a five-year minimum where expected use is five years or longer. Article 13(10) permits patching only the latest substantially modified version when users can upgrade free of charge and without additional costs.
Interpretive reading in C(2026) 5252: Point 126 warns manufacturers against treating five years as a universal default when hardware durability or customer expectations point to longer operational life. Point 130 confirms that routine customer testing and personnel time do not count as additional upgrade costs under Article 13(10), whereas forced hardware replacement does. Point 133 confirms that a substantial modification requires re-evaluating expected use time rather than automatically resetting the support clock.
Class I conformity assessment and harmonised standards
Binding rule: Under Article 32(2) and Article 27, Annex III Class I important products qualify for Module A internal control only when harmonised standards, common specifications, or a qualifying certification scheme are applied.
Interpretive reading in C(2026) 5252: Points 147 to 155 set two cumulative conditions for Class I self-assessment. Every applicable requirement of the relevant harmonised standard must be applied in full, and the standard’s scope must cover all cybersecurity risks of the product’s core functionality. Secondary features outside the standard’s scope must still be addressed in the Article 13(2) risk assessment, while presumption of conformity reaches only the core functionality covered by the cited standard.
Frequently asked questions
Is Commission guidance C(2026) 5252 legally binding?
No. Point 8 of C(2026) 5252 states that the guidance is not legally binding on economic operators. Only Regulation (EU) 2024/2847 is binding Union law, and only the Court of Justice of the European Union can give an authoritative interpretation of the Regulation. National market surveillance authorities and notified bodies nonetheless rely on C(2026) 5252 as their operational benchmark.
Does a five-year support period satisfy CRA Article 13(8) for every product?
No. Article 13(8) requires the support period to reflect the time the product is expected to be in use, with five years acting as a minimum floor unless expected use time is shorter. Point 126 of C(2026) 5252 states that five years is not a default for products reasonably expected to stay in use longer, such as industrial controllers or network infrastructure.
When is a software update a substantial modification under C(2026) 5252?
Under point 110 of C(2026) 5252, an update is assessed against four questions: whether it introduces new threat vectors, enables new attack scenarios, increases the likelihood of known scenarios, or increases their potential impact, measured against the existing risk assessment. Even a security update becomes a substantial modification under point 109 if it adds external service dependencies or changes product boundaries beyond the assessed purpose.
Work out where your own product lands
Free CRA classification, a vulnerability disclosure portal on your own domain, and Article 14 deadline tracking.