Cyber Resilience Act for software and apps: am I affected?
4 min read
Many software vendors think the Cyber Resilience Act is a matter for device manufacturers. It is not: standalone software is a product with digital elements too. This guide shows which software is covered, where the line to web applications and SaaS runs and what applies from when.
Which software falls under the Cyber Resilience Act
A product with digital elements is any software or hardware product and its remote data processing solutions, including software components placed on the market separately (Art. 3(1)). According to the Commission guidelines, software is covered where it is provided to the user and runs on the user's own system – downloaded, installed or otherwise supplied.
- apps from an app store running on a smartphone
- desktop programs, even if built with web technologies and packaged for local execution
- browser extensions
- libraries, SDKs and other components that you supply to customers
The data connection required by Art. 2(1) can also be indirect: according to the Commission FAQ, even an offline text editor is indirectly connected via the operating system. Anyone making software available in the course of a commercial activity – whether for payment or free of charge – should therefore assume they are affected.
Source: Art. 2(1) CRA · Art. 3(1), (22) CRA · Commission guidance C/2026/6013, points 18–20, Examples 3, 4 · Commission FAQ on the CRA, 1.3
Web applications and SaaS
Software that runs on someone else's servers and is only used through the browser is not, on that basis alone, a product with digital elements according to the guidelines. The same applies to websites. SaaS, PaaS and IaaS services instead fall under the NIS 2 Directive where the provider is at least a medium-sized enterprise (Recital 12).
The line is narrow, though: if your app, desktop client or device needs a backend that you developed yourself in order to perform one of its functions, that backend is part of the product as remote data processing (Art. 3(2), Recital 11). If you use a third-party SaaS service, that is not remote data processing – the Commission recommends treating it like a bought-in component and taking it into account in the risk assessment.
Source: Art. 3(2) CRA · Recital 11 CRA · Recital 12 CRA · Commission guidance C/2026/6013, point 21, Examples 5, 6, Section 8.3.3
Source code, open source and test versions
- If you license source code to customers, you place a product on the market – even if the customer still adapts and compiles the code. You are not responsible for their adaptations.
- Free and open-source software shared on public repositories is generally not considered placed on the market according to the guidelines. A commercial activity can, however, already exist if you charge more than cost for support or make a profit through a platform, for example (Recital 15).
- Unfinished software such as alpha and beta versions may be made available for the time needed for testing, even if it does not yet comply with the Cyber Resilience Act.
Source: Recital 15 CRA · Commission guidance C/2026/6013, points 22–24, Example 7, footnote 8
Which software faces stricter checks
For most programs, self-assessment is sufficient. However, Annex III lists software categories with stricter procedures, including:
- Class I: identity management systems, browsers, password managers, software that searches for, removes or quarantines malicious software, VPN products, network management systems, SIEM systems, boot managers, PKI software, operating systems
- Class II: hypervisors and container runtime systems, firewalls, intrusion detection and prevention systems
What matters is the core functionality: a news app with an embedded browser does not become a browser within the meaning of the Annex. Our guide on important and critical products describes all categories and procedures.
Source: Art. 7(1) CRA · Annex III, Classes I, II CRA · Implementing Regulation (EU) 2025/2392, Recitals 2 and 3
Updates and versions
New versions without a substantial modification need no new conformity assessment and do not change the date of placing on the market. Our guide on substantial modification explains when an update does count as a new product. During the support period – as a rule at least five years – you provide security updates.
Source: Commission guidance C/2026/6013, point 15 · Art. 13(8) CRA
What applies from when
- Since 11 September 2026: reporting obligation for actively exploited vulnerabilities and severe incidents – including for software already on the market before (Art. 14, Art. 69(3), Art. 71(2)).
- From 11 December 2027: all other obligations (Art. 71(2)).
- Software placed on the market before 11 December 2027 only has to meet the requirements if it is substantially modified later (Art. 69(2)).
Source: Art. 14 CRA · Art. 69(2), (3) CRA · Art. 71(2) CRA
In practice
- Clarify what you deliver: installed software, a client with its own backend or a pure web service.
- Record your own backends as part of the product; treat third-party cloud services like components.
- Generate a software bill of materials (SBOM) from the build – the basis for vulnerability handling and evidence.
- Organise the reporting obligation – it already applies today, including to versions in the field.
Related guides
Terms in the Cyber Resilience Act glossary
Sources
- Regulation (EU) 2024/2847, Art. 2, 3, 7, 13, 14, 69, 71, Annex III, Recitals 11, 12, 15 (EUR-Lex, Official Journal)
- Commission guidance C/2026/6013, OJ C, 17 Nov 2026, Sections 2.1–2.3 and 8.3.3 (non-binding)
- Commission FAQ on the Cyber Resilience Act, version 1.4 of 4 September 2026, 1.3
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 31 Oct 2026, last updated 31 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.