ambolt

CRA for open-source maintainers and stewards: what applies

As of 6 October 2026, the Cyber Resilience Act (Regulation (EU) 2024/2847) applies to products made available on the EU market in the course of a commercial activity; free and open-source software developed or supplied outside of a commercial activity is not covered (Article 3 and the recitals on open-source software). Organisations that systematically support such software for commercial use are "open-source software stewards" with lighter duties under Article 24. A company that ships open-source software in its own product is a manufacturer with the full duties.

Three situations

SituationRoleWhat applies
Individual or community project, not monetised, no commercial intentOutside the RegulationNo CRA obligations on that project; commercial users who integrate it carry the duties for their product
Foundation or company that systematically supports specific FOSS products intended for commercial useOpen-source software steward (Article 3)Article 24
Company that puts the software into a product it sells or monetisesManufacturer (Article 3)Articles 13, 14 and the rest

What counts as commercial activity

The recitals explain that a commercial activity can include charging a price, or monetising a product in other ways, for example by charging for technical support where that does not serve only to recover actual costs, by providing a software platform through which the manufacturer monetises other services, or by requiring personal data for reasons other than security or compatibility. Accepting donations without the intention of making a profit is not, in itself, treated as commercial, but donations that exceed the costs of design, development and provision can be. Read recitals 15, 18, 19 and 20 for the exact wording.

What a steward must do (Article 24)

  1. Put in place and document a cybersecurity policy that fosters the development of a secure product and effective vulnerability handling by the developers, including a policy for voluntary reporting of vulnerabilities.
  2. Cooperate with market surveillance authorities on request, to reduce cybersecurity risks.
  3. Apply the reporting rules of Article 14(1) (actively exploited vulnerabilities) to the extent the steward is involved in the development of the products, and Article 14(3) and (8) for severe incidents that affect the network and information systems the steward provides for development (Article 24(3)). Article 14 applies from 11 September 2026 (Article 71(2)). The exact scope is discussed in public by the Open Regulatory Compliance working group; check before you rely on one reading.

Open-source software stewards are exempt from administrative fines for infringements of the Regulation (Article 64(10)(b)).

What to do

  1. Decide which of the three situations is yours; write the reasoning down.
  2. If you are a steward, publish the cybersecurity policy and a vulnerability disclosure policy with a contact.
  3. Recommended, not required of stewards: publish a per-release SBOM so manufacturers who depend on you can do their due diligence (their duty is in Article 13(5)).
  4. Have a person ready to handle Article 14 reports if you are involved in development; see reporting obligations.
  5. Run the classifier and the repository check for your project.

Manufacturers who use your software have to report vulnerabilities they find in components to the person maintaining them (Article 13(6)); expect such reports.

Article references

Article 3 (definitions); Article 13(5) and 13(6); Article 14; Article 24; Article 64(10); Articles 69 and 71; recitals 15, 18, 19 and 20.

This is general information, not legal advice. It does not say that any project is compliant or certified.

Free tools

Information generated from your inputs, with article references to Regulation (EU) 2024/2847. It is not legal advice and does not replace your own assessment; check the references against the Official Journal.