On this page
- Which of my products does the CRA cover?
- Is my SaaS in scope?
- Am I a manufacturer if I sell a plugin or theme?
- Does it apply if I sell from outside the EU?
- What is a free plugin maintainer or a "steward"?
- What exactly do I have to report now?
- What should a small vendor do this week?
- Which questions settle my position?
- What changes on 11 December 2027?
- What we could not confirm
The Cyber Resilience Act (CRA) applies to software you ship to customers, such as a plugin, theme or app that connects to a network. It does not apply to a standalone SaaS, unless that service is the remote part a downloadable product needs to work. Since 11 September 2026, makers of in-scope products must report actively exploited vulnerabilities.
| Fact | Detail | Source |
|---|---|---|
| Law | Regulation (EU) 2024/2847, the Cyber Resilience Act | EUR-Lex |
| Standalone SaaS | Not a product with digital elements | Commission Q&A, scope |
| Downloadable software and apps | In scope when they have a direct or indirect data connection (Article 2(1)) | Commission Q&A, scope |
| Reporting duty starts | 11 September 2026 | Commission Q&A, transition |
| Full product requirements start | 11 December 2027 | Commission Q&A, transition |
| Official guidance | Commission guidance C(2026) 5252, published 27 July 2026 | Commission guidance |
| Checked | 4 November 2026 | this page |
Which of my products does the CRA cover?
The test is the product, not the company. A product with digital elements is software or hardware with a direct or indirect logical or physical data connection to a device or network (Article 2(1), as quoted in the Commission's scope answers). Software people download and run, on a laptop, a phone or a web server, fits that description.
The Commission gives an example that matches a plugin closely: standalone software that can be downloaded and installed on a device, such as an app from an app store or a program downloaded from a website. A WordPress plugin or theme is installed on the customer's own server and talks to a network. It sits on the in-scope side.
A website is different. The Commission says websites that do not support the functionality of a product with digital elements are not products with digital elements themselves. Your marketing site and your documentation are not what the Act regulates.
Is my SaaS in scope?
A standalone SaaS or other cloud service, designed and developed outside the responsibility of a manufacturer, is not a product with digital elements. If you run a hosted tool that customers log into and nothing is installed on their side, the Act does not treat it as a product.
The catch is remote data processing. The Commission describes this as data processing designed by or under the responsibility of the manufacturer, in a way that the product's functions depend on it (Article 3(2)). If your mobile app cannot work without your backend, the backend is not a separate SaaS in the Act's eyes. It is part of the product.
That is the question to ask for each service you run: could the downloadable product do its job without it? If not, expect the service to be pulled into the product's scope. The Commission guidance of 27 July 2026 covers remote data processing in detail, and you should read its section on it before deciding. We could not extract the PDF's body as text, so we do not summarise it here.
Am I a manufacturer if I sell a plugin or theme?
A manufacturer is a person who develops or manufactures a product with digital elements and markets it under their own name or trademark (Article 3(13), per the working group's manufacturer FAQ). How the product was financed or built does not matter. What matters is whose name is on it.
If you sell a plugin under your own brand, you fit that definition. Selling through a marketplace does not change who the manufacturer is. WPBay's guidance to sellers says the law applies regardless of where the seller is based, and that commercial open-source products are not automatically exempt. That is a marketplace's reading, so treat it as a pointer.
If you build plugins for a client who ships them under the client's name, the client may be the manufacturer. Your contract should say who files a report when one is needed.
Does it apply if I sell from outside the EU?
The Act attaches to products made available on the EU market. A seller based elsewhere who lets EU customers buy a download is within reach of the rules. WPBay reaches the same view for its sellers.
Authorised representatives and importers are covered in the regulation itself. Read those articles before you sell to EU customers at scale.
What is a free plugin maintainer or a "steward"?
The CRA draws a line between selling software and publishing it. An open-source software steward is a legal person, other than a manufacturer, whose purpose is to support free and open-source software on a sustained basis, where that software is ultimately meant for commercial activity. Foundations are the usual example.
The working group's stewards FAQ lists their duties as deliberately light. They keep a cybersecurity policy and a vulnerability handling process, cooperate with authorities, and report actively exploited vulnerabilities and severe incidents in specific cases. SBOMs, technical documentation and the full essential requirements do not apply to them.
The same FAQ says an individual who maintains a project alone is typically not a steward, because a steward must be a legal entity, and is generally not a manufacturer, because they do not place a product on the market. Several answers on that page are marked as pending Commission guidance, so read that as the working group's view as of 24 October 2026. We could not confirm from a primary source the date from which the steward reporting duty applies, so check the regulation.
What exactly do I have to report now?
The reporting duty started on 11 September 2026 and applies to products placed on the market before 11 December 2027 as well (Commission Q&A, reporting). For those older products it is a notification duty only. The Commission says manufacturers are not required to meet the other obligations, such as vulnerability handling, for them yet.
| What happens | Reportable? | Source |
|---|---|---|
| A bug is found by a researcher, no sign anyone abused it | No | Commission Q&A |
| A CVE is assigned to your plugin | No, not on its own | WPBay |
| You have reliable evidence a malicious actor exploited a flaw in a system without permission | Yes | Commission Q&A |
| A vulnerability in a component you bundle is exploitable in your product | Yes, both you and the component's maker | Commission Q&A |
| A severe incident affecting the security of your product | Yes | Commission Q&A, transition |
The Commission defines an actively exploited vulnerability as one for which there is reliable evidence that a malicious actor has exploited it in a system without permission. A zero-day is not reportable just because it is unknown. It becomes reportable when the same evidence test is met, and otherwise reporting it is optional (checked 24 October 2026).
The Commission's reporting page sets the clock: an early warning within 24 hours of becoming aware, a full notification within 72 hours, then a final report within 14 days after a corrective measure is available for a vulnerability, or within one month of the 72-hour notification for a severe incident. Reports go through ENISA's CRA Single Reporting Platform. WPBay's guidance gives its sellers the same deadlines and asks them to tell the marketplace as well. What a small vendor actually files in the first 24 hours has its own walkthrough.
What should a small vendor do this week?
The reporting clock starts when you become aware, so the work is being able to become aware. A seller with no way to learn that a plugin is under attack has a process gap to close before any legal question.
- List every product you ship and mark each one downloadable, hosted, or both.
- For each hosted service, write down whether a downloadable product needs it to work.
- Name the legal entity whose name or trademark is on each product.
- Name the person who decides that evidence of exploitation is reliable, and a backup.
- Set up one inbox and one on-call route for reports from customers, researchers and your hosting provider, and publish how researchers may test and report.
- List the third-party components you bundle and who you would notify if one is exploited.
- Write a customer notice template that says affected versions, the fix and what to do, without exploitation detail.
- Keep a dated log of who learned what and when, because the deadlines run from awareness.
If a customer reports a compromise, our incident response playbook covers the first hours. For the supply-chain side of the same duty, see the pattern of vendor-held trust and the case of a plugin sold and then backdoored. If you sell plugins, which ones hold remote-control keys shows what your own customers worry about, and the other compliance guides cover the audit side.
Which questions settle my position?
We sell [product] under [brand] to customers in the EU, and a separate hosted service that the product connects to. Is the hosted service remote data processing under Article 3(2)? Are we the manufacturer, and do we need an authorised representative? Who files a report, with which evidence threshold, and from which date does each of our products fall under the full requirements?
Answer them product by product, using the list from the checklist above.
What changes on 11 December 2027?
On that date the full requirements apply, and manufacturers must ensure products conform to the essential cybersecurity requirements. Market surveillance and enforcement provisions start then too (Commission Q&A, transition).
| Date | What applies | Source |
|---|---|---|
| 11 June 2026 | Member States designate notifying authorities (Articles 35 to 51) | Commission Q&A |
| 11 September 2026 | Reporting of actively exploited vulnerabilities and severe incidents | Commission Q&A |
| 11 December 2027 | Essential cybersecurity requirements, market surveillance and enforcement | Commission Q&A |
Units already placed on the market before 11 December 2027 do not need to meet the full requirements. A manufacturer cannot produce additional units of a non-compliant product type after that date. Software that you keep changing is the hard case: the Commission guidance has a section on substantial modification, so read it before you plan releases past that date.
What we could not confirm
The penalties, the five-year support period, the treatment of microenterprises and the rules for authorised representatives are all in the regulation, and EUR-Lex returned an empty page to our fetch on 4 November 2026. We left those figures out rather than repeat them from a secondary page. The regulation on EUR-Lex holds them.
Questions people ask
Does the Cyber Resilience Act apply to my SaaS?
A standalone SaaS is not a product with digital elements, so the CRA does not cover it as such. The exception is a remote service that you design as part of a product and that the product needs to do its job. That service is treated as part of the product.
I sell a WordPress plugin or theme. Do I have to report vulnerabilities?
If you sell it under your own name or brand, you are very likely a manufacturer. Since 11 September 2026 a manufacturer must report an actively exploited vulnerability, meaning one with reliable evidence of exploitation. A bug that is merely found or assigned a CVE does not trigger the duty.
I am outside the EU. Does the CRA still reach me?
It applies to products made available on the EU market, wherever the seller is based. If EU customers can buy and download your plugin, it applies.
I give my plugin away for free and I am the only maintainer. Am I covered?
The working group that tracks the CRA says a solo maintainer is typically neither a steward nor a manufacturer, because a steward must be a legal person and a manufacturer must market the product. That changes if you sell support, a pro version or a hosted service.
Do I need to do anything about the CRA this week?
Decide which of your products are downloadable, work out whether you are the manufacturer, and write down who files a report and how you would learn that a bug is being exploited. The reporting duty has applied since 11 September 2026, while the full product requirements start on 11 December 2027.
My product was sold before December 2027. Is it exempt?
Only from the full product requirements. The Commission says units already placed on the market before 11 December 2027 do not need to comply with them. The reporting duty is different: it applies to products placed on the market before that date as well.
Sources
- Commission guidance on the application of Regulation (EU) 2024/2847, C(2026) 5252 final, Annex (27 July 2026)The Commission's own guidance. Covers remote data processing and free and open-source software. We confirmed its title, reference and date; the PDF did not extract as text for us, so no claim on this page rests on its body.
- Regulation (EU) 2024/2847 (Cyber Resilience Act), EUR-LexThe law itself. The article numbers cited on this page are the ones quoted in the Commission Q&A below. EUR-Lex returned an empty page to our fetch on 4 November 2026.
- CRA Q&A mirror: Commission answers on scope (cra.orcwg.org)Standalone SaaS, websites and downloadable software, as answered by the Commission. Read on 24 October 2026.
- CRA Q&A mirror: Commission answers on reporting obligationsDefinition of actively exploited, start date, third-party components. Read on 24 October 2026.
- CRA Q&A mirror: Commission answers on the transition periodWhat applies from 11 June 2026, 11 September 2026 and 11 December 2027. Read on 24 October 2026.
- Open Regulatory Compliance Working Group: manufacturers FAQManufacturer definition (Article 3(13)). Working-group commentary, not the Commission.
- Open Regulatory Compliance Working Group: open-source software stewards FAQSteward definition, light-touch duties, solo maintainers. Working-group commentary; several answers are marked pending guidance.
- Open Regulatory Compliance Working Group: official Commission guidance indexSource for the title, reference and date of the Commission guidance.
- WPBay: CRA reporting requirements for sellersA marketplace's reading of the 24 hour, 72 hour, 14 day and one month deadlines and of non-EU sellers. A marketplace document, not law; check Article 14 of the regulation.
- European Commission: CRA reporting obligationsThe Commission's reporting page, last updated 11 September 2026. Deadlines, start date and ENISA's Single Reporting Platform. Read on 4 November 2026.
- Envato Help: CRA reporting requirements for software authorsA marketplace's guidance for authors. It returned HTTP 403 to our fetch on 24 October 2026, so nothing on this page is taken from it.
Facts on this page are dated and point at the primary source next to them. If a vendor status changes after the date shown, the vendor's page wins; tell us at support@run.cloud and we will update it.