Article 24

Obligations of Open-Source Software Stewards Under the CRA

Article 24 introduces the concept of 'open-source software steward' — an entity that provides a platform or support for the ongoing development of open-source software used in products with digital elements, without placing a product on the market itself. Open-source stewards are not manufacturers and are not subject to CE marking or EU Declaration of Conformity obligations. However, they must put a cybersecurity policy in place, publish a vulnerability disclosure process, and cooperate with market surveillance authorities — recognising their structural role in the supply chain.

Effective: September 2026Applies to: Non-profit foundations managing open-source software widely used in CRA-regulated productsLast reviewed: 18 October 2026Verified against: the final text of Regulation (EU) 2024/2847
Source: Regulation (EU) 2024/2847, Article 24, official text on EUR-Lex

Who Is an Open-Source Software Steward?

An open-source software steward is defined as a legal person (not an individual) that:

  1. Provides a platform or environment for the development or distribution of open-source software intended for integration into products with digital elements
  2. Does so on a non-commercial basis — or where commercial activities do not constitute the primary purpose
  3. Does not place products on the market itself in a way that makes it a manufacturer under Article 13
  • Linux foundations and similar non-profit organisations managing major open-source projects
  • Public benefit entities maintaining security libraries, cryptographic toolkits, or operating system components
  • Academic institutions managing software repositories used in commercial products

Individual developers who contribute to open-source projects — but do not manage the overall platform — are explicitly excluded from the steward definition.

CRA reference:Article 24(1)

The Cybersecurity Policy Requirement

Article 24 requires open-source software stewards to put in place and document a cybersecurity policy covering:

  • How security vulnerabilities in the managed software are identified, assessed, and addressed
  • The processes by which security patches and updates are developed and released
  • How external vulnerability reports are received and handled
  • How the steward communicates security information to downstream users (manufacturers integrating the software)

This policy need not be as comprehensive as a manufacturer's full security development lifecycle documentation, but it must be documented and publicly accessible. The policy demonstrates that the steward takes a structured approach to security rather than an ad hoc one.

CRA reference:Article 24(2)

Vulnerability Disclosure for Open-Source Stewards

Article 24 requires open-source software stewards to operate a process for receiving and handling vulnerability reports — essentially a CVD policy equivalent. This process must:

  • Provide a publicly accessible mechanism for reporting vulnerabilities (typically a security.txt file, a SECURITY.md in the repository, or a dedicated reporting form)
  • Acknowledge receipt of vulnerability reports
  • Provide reporters with a process timeline and coordinate disclosure
  • Publish security advisories when vulnerabilities are fixed

Article 24(3) does extend parts of Article 14 to stewards, so the 24-hour and 72-hour clocks are not switched off across the board. How far they reach depends on the kind of support the steward provides, which is set out further below. Where a reporting duty does not apply, voluntary reporting under Article 15 stays open.

CRA reference:Article 24(3)

Cooperation with Market Surveillance Authorities

Article 24(2) requires open-source software stewards to cooperate with market surveillance authorities, at their request, to mitigate the cybersecurity risks of a product that qualifies as free and open-source software.

After a reasoned request from a market surveillance authority, the steward provides the documentation of its cybersecurity policy under Article 24(1), on paper or in electronic form, in a language the authority can easily understand. The duty is narrower than a manufacturer's. A steward documents and shares its policy, and it does not carry the manufacturer obligations of Article 13.

CRA reference:Article 24(2)

What Open-Source Stewards Are NOT Required to Do

To avoid chilling open-source development, Article 24 explicitly carves out several obligations that manufacturers face but stewards do not:

  • No CE marking — open-source stewards do not need to affix CE markings to software
  • No EU Declaration of Conformity — no formal conformity declaration is required
  • No conformity assessment — no notified body involvement is required
  • Article 14 reporting only where the steward is involved — a steward that neither develops the product nor provides the systems used to develop it carries no 24h/72h duty, but Article 24(3) does apply Article 14(1), (3) and (8) to those that do
  • No SBOM requirements — no formal software bill of materials obligation under

Manufacturers who commercialise open-source software (sell it, monetise it, bundle it in commercial products) become manufacturers under Article 13 and lose the steward carve-out. The line between steward and manufacturer is primarily drawn by commercialisation.

CRA reference:Article 24

How far do a steward's reporting duties actually go?

Article 24(3) applies Article 14(1), (3) and (8) to stewards, and Commission guidance C(2026) 5252 makes clear that how far they apply depends on the kind of support the steward provides.

A steward providing only non-technical support, such as managing project branding, laying down governance rules, organising community events or collecting donations, is by definition not involved in developing the product and provides no network and information systems for it. It is not required to report actively exploited vulnerabilities, and not required to report severe incidents. Where it does become aware of an actively exploited vulnerability, for example through a security researcher, it should share the information with the maintainers in line with its cybersecurity policy, and voluntary reporting under Article 15 should be considered.

A steward that provides the underlying IT infrastructure, such as hosting source code repositories, version control or signing keys, must notify ENISA and the CSIRTs under Article 14(3) of severe incidents affecting that infrastructure which have an impact on the security of the products, and inform users where appropriate.

A steward that contributes engineering resources, by employing developers, coordinating development, reviewing or merging code, managing releases or handling vulnerability reports, must additionally notify actively exploited vulnerabilities under Article 14(1) and, where it has a direct relationship with impacted users, inform them under Article 14(8).

A steward is likely to learn of active exploitation through downstream reports, because the component sits inside other products. An entity that stops providing sustained support may cease to be a steward, and is encouraged to communicate that change clearly.

CRA reference:Article 24(1) to (3); Commission guidance C(2026) 5252 points 79 to 84 and 216

Work through Article 24 for each product in one CRA workspace.

Classify the product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Does my open-source project need to register with anyone to be treated as a steward?+

No registration is required to be treated as an open-source software steward. The classification is determined by whether your entity and activities meet the Article 24 definition. ENISA provides guidance to help organisations self-assess their steward status. Documenting the basis for steward classification is advisable in case of MSA scrutiny.

What if our foundation has some commercial revenue (e.g., training, consulting)?+

Article 24's 'non-commercial' requirement does not mean zero revenue. A foundation with incidental commercial activities (consulting, training, hosted services) may still qualify as a steward if the primary purpose is non-commercial open-source development. The key test is whether the software is placed on the market as a product — if yes, manufacturer obligations apply. If the software is freely available and not sold as a product, steward treatment is likely appropriate.

Are open-source libraries used as components subject to the CRA at all?+

Open-source libraries used as components are regulated through the manufacturers who integrate them. The manufacturer of the final product is responsible for due diligence on the security of integrated components (Article 13(5)). The CRA does not impose direct obligations on open-source component authors who are not stewards, but stewards of widely-used libraries face the Article 24 obligations.

How should we document our steward status in case of market surveillance inquiry?+

Maintain a brief written record explaining: (1) why your entity qualifies as a steward rather than a manufacturer; (2) the published cybersecurity policy covering your projects; (3) your published CVD process. Store this alongside your project's security documentation so it can be produced quickly if an MSA asks questions.

Does a steward have to file the 24-hour and 72-hour reports?+

Article 24(3) applies Article 14(1), (3) and (8) to an open source software steward that develops the product with digital elements or provides the systems used to develop it. A steward outside that description carries no 24-hour or 72-hour duty, and voluntary reporting under Article 15 stays open. CE marking and the EU Declaration of Conformity apply in neither case.

Need a CVD policy for Article 24?

Annex I Part II(5) asks for a coordinated vulnerability disclosure policy. Download a free template.

Browse templates →