Back to all articles

Cyber Resilience Act 2026: are your software, connected devices and electronics already affected?

Share

The Cyber Resilience Act (CRA) did not wait until December 2027 to have legal effects. Since 11 September 2026, manufacturers of products with digital elements made available on the European Union market must report certain actively exploited vulnerabilities and certain severe incidents affecting product security. The broader requirements for secure product design, documentation and conformity will generally apply from 11 December 2027. These are distinct milestones, and confusing them could cause a business to overlook an obligation that already applies.

This is not just a matter for router vendors or large companies. A software publisher, a connected-sensor manufacturer or an SME selling an electronic control board with embedded firmware may fall within the CRA. Recent ENISA technical guidance — its software bill of materials advisory of 22 October and secure update mechanisms advisory of 4 November — gives product teams a practical basis for turning regulatory duties into repeatable engineering processes.

The practical takeaway: identify which products fall in scope, define what events trigger a report, appoint someone who can make notifications, and build a verifiable patching process. A newly published CVE in a dependency, or an arbitrary company IT incident, does not automatically require a CRA notification.

Three important dates: what applies already?

Regulation (EU) 2024/2847 entered into force in December 2024, but its provisions have a staggered application schedule.

Date What changes
11 June 2026 Provisions on the notification of conformity assessment bodies start to apply.
11 September 2026 Article 14 reporting obligations begin for manufacturers: actively exploited vulnerabilities and severe incidents affecting the security of digital products.
11 December 2027 The main cybersecurity, vulnerability-handling, documentation and conformity obligations apply. Specific reporting duties for certain open-source software stewards begin under Article 24(3).

The European Commission confirms that reporting obligations cover products already made available on the EU market, not just new products released after September 2026. By contrast, the main conformity requirements starting in December 2027 are subject to transitional provisions: products placed on the market before that date generally become subject to those other obligations if they undergo a substantial modification after that date. The actual status must be assessed for each product.

Which products and businesses are covered?

The CRA generally addresses software and hardware products with digital elements whose intended or reasonably foreseeable use includes a direct or indirect logical or physical data connection to a device or network, when made available on the EU market in the course of a commercial activity. Manufacturers placing them on the market under their own name or brand carry the corresponding duties. Importers and distributors may also have responsibilities according to their role.

Examples that warrant assessment include:

  • Distributed software: installable applications, specialist engineering tools and some software components marketed separately. How the software is supplied, who is the manufacturer and the applicable exclusions matter.
  • Connected hardware: routers, IoT gateways, electronic controllers, industrial devices with firmware and network-facing configuration interfaces.
  • Hybrid products: a microcontroller, embedded firmware, a configuration UI and a remote processing service necessary to operate the product.
  • 3D-printed objects: a passive printed enclosure without software or electronics is generally not covered by the CRA merely because it was printed. A commercially supplied connected device incorporating that enclosure may be covered.

A prototype developed solely for internal use and not placed on the market should not automatically be treated as a commercial product. Bespoke delivery to a customer is not necessarily exempt: the supply model, the parties' responsibilities and the technical characteristics of the product must be assessed.

Open source requires equal care. A volunteer contributor to a non-commercial project is not automatically a CRA manufacturer, while free and open-source software made available in the course of a commercial activity can fall within manufacturer duties. The Act also creates a separate, lighter regime for open-source software stewards supporting the long-term viability of certain open-source products. See the Commission's open-source explanation and the French cybersecurity authority's overview.

Sector-specific exclusions apply, including products governed by certain medical-device and automotive rules. Having an electronic component is not, by itself, proof that the CRA applies.

Reporting since September 2026: which events and how quickly?

Article 14 of the Regulation establishes two reportable event categories for manufacturers within its scope:

  1. An actively exploited vulnerability contained in the product, once the manufacturer becomes aware of it. A CVE with no reliable evidence of exploitation, a scanner finding or an unsupported suspicion does not by itself establish this reporting category.
  2. A severe incident having an impact on the security of the product, under the severity criteria in the Regulation. Not every cybersecurity incident affecting the manufacturer's corporate IT environment qualifies.

The time limits are calculated from when the manufacturer becomes aware of the reportable event, not simply from the date the vulnerability first appears in a public database.

Submission Legal deadline
Early warning Within 24 hours after becoming aware, without undue delay.
Detailed notification Within 72 hours after becoming aware, including information and mitigation already available.
Final report — actively exploited vulnerability No later than 14 days after a corrective or mitigating measure becomes available.
Final report — severe incident Within one month after submitting the 72-hour incident notification.

Reporting does not replace communication to affected users: Article 14 also addresses informing users of risks and appropriate mitigation or corrective measures. The ENISA Single Reporting Platform FAQ explains the event categories and notification framework.

For a third-party library flaw, the manufacturer first needs to verify the component version actually bundled in each product, the resulting exposure and the evidence of active exploitation. Whether the event meets the reporting criteria should be documented, including when the answer is no.

Where do manufacturers report? ENISA's Single Reporting Platform

Since 11 September, manufacturers within scope use the Single Reporting Platform (SRP) operated by ENISA. It enables a single submission to reach the appropriate authorities. For manufacturers established in France, CERT-FR at ANSSI is the coordinating CSIRT.

ENISA announced the platform launch on 11 September 2026. Its official SRP portal page includes access to the reporting service, manuals and FAQ. The platform received a version 1.3 update on 4 November 2026, and the interface and guidance may continue to change.

Before an incident, an affected manufacturer should identify an authorized reporting representative, list its affected products and versions, establish an escalation process, plan what information can be supplied inside 24 and 72 hours, and prepare a method for informing users.

The SBOM: a living product inventory, not a checkbox

A Software Bill of Materials (SBOM) is a machine-readable inventory of software components and versions. Think of it as a manufacturing bill of materials for software: if a flaw is found in a library, the manufacturer can determine which shipped product versions contain that library.

Under Annex I, Part II of the CRA, the main obligations that apply from 2027 include identifying and documenting components and vulnerabilities, including a machine-readable SBOM containing at least the top-level product dependencies. The regulation does not establish a general duty to publish the entire SBOM openly. Authorities may request technical documentation under the conditions in the Act.

An operational SBOM should be regenerated for each released product version, linked to the artifacts that were actually shipped and kept current as dependencies change. Common formats such as CycloneDX and SPDX can make the inventory machine-processable. ENISA's 22 October 2026 technical advisory describes the SBOM lifecycle, data flows and security threats affecting the inventory process itself.

An incomplete SBOM generated once and never reviewed has little operational value. It must feed into vulnerability intelligence, product impact assessment and patch tracking. Our analysis of the LiteLLM software supply-chain compromise illustrates why dependency and release-artifact provenance matters.

Secure updates: detecting a vulnerability is only half the job

Finding a vulnerability is not sufficient if the manufacturer cannot deliver an authentic patch and recover a device when an update fails. ENISA's 4 November 2026 secure-update advisory, written with SMEs in mind, provides guidance across the software update lifecycle.

A robust update process should address:

  • Authenticity and integrity: sign releases, verify before installation, protect signing keys and control the build pipeline.
  • Distribution: protect version metadata, update endpoints and downloads against substitution or malicious redirection.
  • Applicability and anti-rollback: reject unauthorized or obsolete software versions when returning to them would reintroduce vulnerabilities.
  • Recovery: design for interrupted updates and safe recovery without silently restoring an exploitable version.
  • Evidence: identify which devices or versions remain exposed, which patches were delivered and which updates failed.

Controls should match the product's risk profile, resources and architecture. ENISA's advisory is technical guidance, not certification and not automatic proof of CRA conformity.

Practical example: a connected controller with a 3D-printed case

Consider an SME selling a temperature controller made of a 3D-printed enclosure, a microcontroller, firmware and a web configuration interface.

The passive case is not the main CRA concern. The connected product sold as a complete unit may be. The manufacturer should be able to answer four questions:

  1. Which product is affected? Commercial identifiers, hardware variants, firmware versions, third-party components and the supported lifecycle.
  2. Where is the flaw? TLS library, administration UI, Wi-Fi component, remote service or update mechanism.
  3. Is it actively exploited and does it affect product security? Preserve technical evidence rather than assuming that a published CVE means verified exploitation.
  4. What happens if reporting is required? Triage, report via SRP when the conditions are met, patch, notify users appropriately and provide the required final information.

This is a hypothetical teaching example, not a product sold by GLOV Solutions. 3D printing and technical-object services remain marked as upcoming on the GLOV website.

A four-week preparation plan for SMEs

Week 1 — Map the products. List products and versions still in use, their network functions, legal manufacturers, markets, software dependencies and potential sector-specific exclusions. Nominate a CRA owner and a technical security lead.

Week 2 — Prepare reporting. Document the triggers for a CRA report, who assesses the evidence and who can submit within 24/72 hours. Set up reporting roles and SRP procedures, and draft a customer notification template.

Week 3 — Track software components. Link shipped firmware versions and artifacts to a refreshed SBOM. Monitor component maintainers' advisories and record the reasoning behind product-exposure decisions.

Week 4 — Exercise remediation. Run a tabletop scenario involving an actively exploited vulnerability: detection, triage, mock reporting, signed patch preparation, controlled distribution, failed-update recovery and evidence retention.

In parallel, prepare for December 2027 conformity obligations: product cybersecurity risk assessments, secure-by-design requirements, support-period planning, technical documentation, EU declarations of conformity and CE marking where required, following the conformity-assessment route appropriate to the product. CRA readiness is not achieved merely by creating a spreadsheet of components.

What the CRA does not mean

  • “Every online service is covered.” Not necessarily. The precise scope depends on the classification of the digital product, placing it on the market and the remote data processing that forms part of the product; standalone SaaS should not automatically be treated as a CRA product.
  • “Every CVE must be reported within 24 hours.” No. Article 14 specifically addresses actively exploited vulnerabilities, among other defined events.
  • “The full SBOM must be published to everyone.” No. Maintaining an inventory and providing documentation in defined circumstances are not the same as public release.
  • “All CRA obligations started in September 2026.” No. The main product requirements and general conformity regime mostly apply from December 2027.
  • “CRA replaces NIS2 or DORA.” No. These instruments have distinct purposes and regulated entities. Multiple regimes may apply to one organization.

For GLOV Consulting, this topic connects product and organizational risk assessment, software dependency inventories and verifiable operating processes. Our article on operational resilience in Web3 organizations discusses the importance of responsibilities, continuity and evidence. This publication is educational, not legal advice or an announcement that GLOV's upcoming services are available for purchase.

Information reviewed on 9 November 2026. Official guidance and implementation details may evolve. The status of a specific product calls for a fact-based review of distribution, functionality and applicable rules.

Official sources and technical guidance

Related articles

Back to all articles