Skip to content
Economic operators

Open source and the Cyber Resilience Act: who has which obligations

8 min read

The Cyber Resilience Act only covers open-source software supplied in the course of a commercial activity. Foundations and companies that support projects on a sustained basis have a lighter role: the open-source software steward. Anyone integrating open source remains fully responsible for their product.

When open-source software is covered

Free and open-source software is software the source code of which is openly shared and which is made available under a free and open-source licence that provides for all rights to make it freely accessible, usable, modifiable and redistributable (Art. 3(48)).

What matters is making available on the market: the supply of a product for distribution or use on the Union market in the course of a commercial activity, whether in return for payment or free of charge (Art. 3(22)). Only open-source software supplied in this way falls within the scope of the Regulation (recital 18).

  • Anyone who contributes source code to a project that is not under their responsibility is not covered by the Regulation (recital 18).
  • How the software was developed or financed does not count. Regular releases, financial support or contributions from manufacturers do not in themselves make a project commercial (recital 18).
  • The sole act of hosting on open repositories, in package managers or on collaboration platforms is not making available on the market (recital 20).

The obligations of the Regulation apply from 11 December 2027, the reporting obligations under Article 14 already from 11 September 2026 (Art. 71(2)).

Source: Art. 3(22), (48) CRA · Recital 18 CRA · Recital 20 CRA · Art. 71(2) CRA

Commercial activity: price, monetisation, donations

According to recital 15, a commercial activity may be characterised not only by charging a price for the product but also by:

  • charging a price for technical support services that does not serve only the recuperation of actual costs,
  • an intention to monetise, for instance through a software platform via which other services are monetised,
  • requiring the processing of personal data as a condition for use – unless exclusively for security, compatibility or interoperability,
  • accepting donations that exceed the costs of design, development and provision.

Accepting donations without the intention of making a profit is not a commercial activity (recital 15). Open-source software that is not monetised by its manufacturers is not supplied in the course of a commercial activity. An open-source component intended for integration into other manufacturers' products is only made available on the market if it is monetised by its original manufacturer (recital 18).

The Commission's guidelines (C/2026/6013 of 17 Nov 2026, not binding) give examples: a paid version is placed on the market, the free community version is not (point 52). Paid consultancy or training alongside freely downloadable software does not make it commercial (points 55–56). Nor does a donation link alone – but it does if downloads or security updates are in practice only available to donors (points 61–62).

Source: Recital 15 CRA · Recital 18 CRA · Commission guidance C/2026/6013, points 52, 55–56, 61–62

Manufacturer, steward or not covered at all

  • A manufacturer is a person who develops or manufactures a product (or has it developed or manufactured) and markets it under its name or trademark, whether for payment, monetisation or free of charge (Art. 3(13)). Anyone who supplies open-source software under their own name in the course of a commercial activity is a manufacturer with all manufacturer obligations.
  • An open-source software steward is a legal person, other than a manufacturer, that systematically provides support on a sustained basis for the development of specific open-source products intended for commercial activities, and that ensures the viability of those products (Art. 3(14)).
  • Natural persons cannot be stewards. If they publish open-source software without monetising it, they have no obligations under the Regulation.

According to recital 19, stewards include certain foundations and entities that develop and publish open-source software in a business context, including not-for-profit entities. Sustained support includes, for example, hosting platforms and source code and steering development. Software is intended for commercial activities, for example, where integrating manufacturers contribute to it or finance it on a regular basis.

The role applies per project: the same legal person can be the manufacturer of one project and the steward of another – or of the free community version (guidelines, points 53, 72–74). Not-for-profit organisations that use all earnings after costs to achieve not-for-profit objectives do not act commercially (recital 18) but can be stewards (point 66).

Source: Art. 3(13), (14) CRA · Recital 18 CRA · Recital 19 CRA · Commission guidance C/2026/6013, points 51, 53, 66, 72–74

Obligations of open-source software stewards

Stewards are subject to a light-touch and tailor-made regulatory regime (recital 19). Article 24 requires:

  • Cybersecurity policy: put in place and document it in a verifiable manner. It fosters the development of a secure product, effective handling of vulnerabilities and voluntary reporting under Article 15; it covers documenting, addressing and remediating vulnerabilities and promotes information sharing within the open-source community (para. 1).
  • Cooperation with market surveillance authorities at their request; provision of the policy following a reasoned request (para. 2).
  • Notification of actively exploited vulnerabilities under Article 14(1), to the extent that the steward is involved in development (para. 3).
  • Notification of severe incidents and information of users under Article 14(3) and (8), to the extent that the incidents affect network and information systems the steward provides for development (para. 3).

Stewards do not affix the CE marking (recital 19). Market surveillance authorities supervise Article 24 and require corrective action in case of non-compliance (Art. 52(3)). Administrative fines under Article 64(3) to (9) do not apply to any infringement by stewards (Art. 64(10)(b)). The wording does not mention paragraph 2 there; recital 120, however, assumes that no administrative fines apply to stewards and rules out other penalties of a pecuniary character.

The wording does not state expressly from when the reporting obligations under Article 24(3) apply. In its FAQ, ENISA takes the view that they only apply from 11 December 2027 – this is ENISA's interpretation.

According to the guidelines, the scope of the reporting obligations depends on the type of support: a steward providing only non-technical support (branding, governance rules, donations) does not report; one providing the infrastructure reports severe incidents affecting it; one providing engineering resources also reports actively exploited vulnerabilities (points 79–82).

Source: Art. 24 CRA · Recital 19 CRA · Art. 52(3) CRA · Art. 64(10) CRA · Recital 120 CRA · ENISA FAQ on the Single Reporting Platform, question 29 · Commission guidance C/2026/6013, points 79–82

If you integrate open-source components

Manufacturers exercise due diligence when integrating third-party components so that these do not compromise the cybersecurity of the product – expressly also for open-source software that has not been made available on the market in the course of a commercial activity (Art. 13(5)). The appropriate level depends on the risk of the component. Recital 34 lists possible actions:

  • verifying whether the manufacturer of the component has demonstrated conformity, for instance via the CE marking,
  • verifying that the component receives regular security updates,
  • verifying that it is free from vulnerabilities registered in the European vulnerability database or other publicly accessible databases,
  • carrying out additional security tests.

If you identify a vulnerability in an integrated component, report it to the person or entity manufacturing or maintaining the component, and address and remediate it in accordance with Annex I, Part II. If you have developed a fix yourself, share the relevant code or documentation, where appropriate in a machine-readable format (Art. 13(6)).

According to the guidelines, you only report for the version you integrate and only what exists in the component itself; no report is needed if you can confirm that the maintainer is aware of the vulnerability or if there is no maintainer any more; you share fixes in a manner compatible with the licence (points 223–227). You do not become responsible for the component itself, even if you contribute code (point 86).

Source: Art. 13(5), (6) CRA · Recital 34 CRA · Commission guidance C/2026/6013, points 86, 223–227

Open-source important products

A manufacturer placing on the market an open-source product that falls under Annex III (important products) can demonstrate conformity using any of the procedures in Article 32(1) – including internal control (module A) without a notified body. The condition: the technical documentation is made available to the public at the time of placing on the market (Art. 32(5), recital 91).

Source: Art. 32(5) CRA · Recital 91 CRA

Voluntary security attestation

To facilitate the due diligence obligation under Article 13(5), the Commission may establish voluntary security attestation programmes for open-source software by delegated act. Developers, users and other third parties could use them to assess conformity with all or certain requirements (Art. 25). According to recital 21, a European cybersecurity certification scheme is also an option; integrating manufacturers, users or public administrations could also initiate or finance an attestation.

Article 25 is an empowerment of the Commission: attestation programmes only exist once it adopts the delegated act. In Germany, the implementing act passed by the Bundestag on 15 October 2026 provides for support for SMEs and open-source software stewards (new section 67 BSIG, including training and a regulatory sandbox); it has not yet been promulgated.

Source: Art. 25 CRA · Recital 21 CRA

In practice

Our recommendations – not requirements of the Regulation:

  • Projects and foundations: record for each project whether you monetise it and whether you support it on a sustained basis. This determines the role: manufacturer, steward or none.
  • Stewards: write down the cybersecurity policy (reporting channel, process up to remediation, security advisories) and file it with a date.
  • Stewards with their own infrastructure: sort out access to the ENISA Single Reporting Platform in advance.
  • Manufacturers: maintain an SBOM and check and document the maintenance status, updates and known vulnerabilities of each open-source component.
  • Manufacturers: record the reporting channels of integrated projects (SECURITY.md, security.txt) in advance.

Related guides

Terms in the Cyber Resilience Act glossary

Sources

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 6 Nov 2026, last updated 6 Nov 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.