EU Product Liability Directive (Directive (EU) 2024/2853)
Extends strict product liability to software, AI systems and digital manufacturing files, including liability for cybersecurity vulnerabilities and failure to supply updates. Member states must transpose by 9 December 2026.
| Jurisdiction | European Union |
|---|---|
| Category | Cybersecurity |
| Status | Upcoming |
| Effective date | |
| Latest development |
Analysis
Directive (EU) 2024/2853 modernises EU product liability law to explicitly cover software, AI systems and digital manufacturing files, including cybersecurity-related defects and failure to supply updates, and must be transposed by Member States by 9 December 2026.Directive (EU) 2024/2853 – EUR‑Lex consolidated page Official Journal PDF – Directive (EU) 2024/2853 Publication detail – EU Official Publications
Below is a compliance‑focused analysis tailored to cybersecurity and software/AI providers.
Key Requirements
1. Extended definition of “product” to include software, AI and digital files
- Software (including AI systems) and digital manufacturing files are explicitly treated as “products” for strict product liability purposes.
- The Directive defines scope to cover products placed on the market or put into service after 9 December 2026, and expressly includes software and digital manufacturing files.Directive (EU) 2024/2853 – EUR‑Lex consolidated page Article 2 – Scope (Lexiara mirror of Directive) Official Journal PDF – Directive (EU) 2024/2853
- Free and open‑source software developed or supplied outside a commercial activity is excluded from the Directive’s scope.
- Article 2 explicitly excludes “free and open-source software that is developed or supplied outside the course of a commercial activity.”Article 2 – Scope (Lexiara) Directive (EU) 2024/2853 – EUR‑Lex Official Journal PDF – Directive (EU) 2024/2853
2. Strict liability for defects including cybersecurity vulnerabilities
- The Directive maintains strict (no‑fault) liability for producers where a product is defective and causes damage, now including software and AI defects such as cybersecurity vulnerabilities that compromise safety.
- The Directive redefines “defect” in a technology‑neutral way, focusing on safety a person is entitled to expect, which can include cybersecurity performance.Directive (EU) 2024/2853 – EUR‑Lex Official Journal PDF – Directive (EU) 2024/2853 European Commission – Product liability reform information page
- Cybersecurity vulnerabilities and failure to implement or maintain appropriate security measures can be treated as defects in the product’s safety, triggering liability when they cause damage.
- Guidance and analyses highlight that the Directive explicitly integrates cybersecurity into the notion of product safety, recognising vulnerabilities and inadequate updates as defects.European Union – Product Liability Reform factsheet (EFTA/EEA‑Lex) Understanding the Product Liability Directive (Streamlex commentary linking official text) EU Product Liability Reform overview – Regulations.ai
3. Liability for failure to supply safety and cybersecurity updates
- Failure to provide necessary updates and patches (including security updates) can make the product defective and trigger liability.
- The Directive introduces post‑sale obligations linking defects to failures in providing updates necessary to maintain safety, especially for connected, software‑driven products.Directive (EU) 2024/2853 – EUR‑Lex Official Journal PDF – Directive (EU) 2024/2853 EU Product Liability Reform overview – Regulations.ai
- Liability can arise even after the product is placed on the market, where subsequent failures to update or patch known vulnerabilities lead to damage.
- Analyses of the Directive stress its coverage of “post‑sale defects” and update obligations over the lifecycle of digital products.EU Directive 2024/2853 analysis – CMS Law Understanding the Product Liability Directive – Streamlex EU Product Liability Reform – Regulations.ai
4. Broadened set of liable economic operators
- Liability is no longer limited to traditional manufacturers; it is extended to software developers, AI providers, platform operators, importers, authorised representatives and certain service providers in the supply chain.
- The Directive updates the concept of “producer” to cover a broad range of economic operators involved in making products (including software/AI) available on the market.Directive (EU) 2024/2853 – EUR‑Lex Official Journal PDF – Directive (EU) 2024/2853 EU Product Liability Reform overview – Regulations.ai
- Online platforms and marketplaces can fall within liability scope when they “present themselves” as providers of the product or control distribution.
- The modernisation of the Directive expressly targets online intermediaries and platform‑based distribution models.Directive (EU) 2024/2853 – EUR‑Lex EU Directive 2024/2853 analysis – CMS Law Product Liability Reform factsheet – EEA‑Lex
5. Presumptions and evidentiary facilitation for injured parties
- The Directive introduces presumptions of defect and causality and eases the burden of proof in complex digital and AI cases.
- New rules allow courts to presume defectiveness or causation when certain conditions are met, acknowledging the difficulty for individuals to prove defects in sophisticated technology.Directive (EU) 2024/2853 – EUR‑Lex Official Journal PDF – Directive (EU) 2024/2853 EU Product Liability Reform overview – Regulations.ai
- Courts can order disclosure of relevant technical information from producers, including data and documentation about AI systems and cybersecurity controls.
- The Directive creates transparency and disclosure obligations in litigation to balance information asymmetries between users and providers.Directive (EU) 2024/2853 – EUR‑Lex Article 19 – Transparency (Lexiara) Official Journal PDF – Directive (EU) 2024/2853
6. Scope, temporal application, and exclusions
- Application date: The Directive applies to products placed on the market or put into service after 9 December 2026.
- Article 2 states that the Directive applies to products placed on the market or put into service after that date.Article 2 – Scope (Lexiara) Directive (EU) 2024/2853 – EUR‑Lex EU Directive 2024/2853 analysis – CMS Law
- Transposition deadline: Member States must transpose the Directive by 9 December 2026, and it repeals Council Directive 85/374/EEC.
- The Directive sets a fixed deadline for national implementation and expressly repeals the previous product liability Directive.Directive (EU) 2024/2853 – EUR‑Lex EU Product Liability Reform overview – Regulations.ai Official Journal PDF – Directive (EU) 2024/2853
Compliance Challenges
1. Mapping liability across complex software and AI supply chains
- Organizations struggle to identify who is the “producer” in multi‑layered AI and software ecosystems (e.g., model provider, API host, integrator, OEM).
- Legal analyses note the difficulty in attributing responsibility among multiple economic operators involved in AI systems.EU Directive 2024/2853 analysis – CMS Law Understanding the Product Liability Directive – Streamlex EU Product Liability Reform overview – Regulations.ai
- Cloud services, SaaS offerings and platforms that deploy models can face ambiguous liability exposure where responsibility for updates and security is shared.
- Commentary on the Directive highlights uncertainties regarding liability allocation in cloud‑based and platform‑based configurations.EU Directive 2024/2853 analysis – CMS Law Product Liability Directive explainer – Streamlex European Product Liability Reform summary – EEA‑Lex factsheet
2. Demonstrating adequate cybersecurity and secure development practices
- To mitigate liability, organizations must show robust cybersecurity measures and secure development lifecycle practices, but many lack comprehensive documentation.
- The Directive’s focus on cybersecurity as part of product safety interacts with standards such as ISO/IEC 27001 and secure‑by‑design principles, requiring evidence of appropriate controls.Directive (EU) 2024/2853 – EUR‑Lex EU Product Liability Reform overview – Regulations.ai ISO/IEC 27001:2022 – Information security management systems (ISO official)
- Organizations often face gaps between regulatory expectations and existing security practices, especially for legacy software and AI models embedded in products.
- Industry analyses of EU cybersecurity and AI regulation (e.g., NIS2 and AI Act) show persistent implementation gaps that will now have product liability implications.NIS2 Directive – EUR‑Lex EU AI Act – EUR‑Lex Regulation (EU) 2024/2803 ENISA – Cybersecurity in digital products report
3. Lifecycle management of updates and vulnerability handling
- Ensuring timely, documented security updates for software and AI models over the product life can be operationally complex, particularly for distributed IoT and embedded devices.
- The Directive’s emphasis on post‑sale update obligations clashes with fragmented patching practices across industries.Directive (EU) 2024/2853 – EUR‑Lex EU Product Liability Reform – Regulations.ai ENISA – “Vulnerability management” guidance
- Organizations must align vulnerability disclosure, patch development, deployment and customer communication, which many do not yet treat as a regulated process.
- ENISA and other EU bodies have published guidance on coordinated vulnerability disclosure and secure software lifecycle that many firms are still adopting.ENISA – Coordinated Vulnerability Disclosure (CVD) guide ENISA – Secure Software Development lifecycle publications NIS2 Directive – EUR‑Lex
4. Evidence, logging and explainability for AI systems
- Because the Directive enables courts to order disclosure and facilitates presumptions of defect, providers must maintain detailed logs, technical documentation and explainability artefacts for AI systems.
- The new evidentiary tools require organizations to demonstrate how AI systems behave, are trained, and are updated, creating a need for robust governance.Directive (EU) 2024/2853 – EUR‑Lex Article 19 – Transparency (Lexiara) EU Product Liability Reform – Regulations.ai
- For high‑risk AI systems, obligations under the AI Act (documentation, logging, risk management) intersect with product liability expectations, and organizations may struggle to harmonize the two regimes.
- The AI Act imposes detailed technical documentation and logging duties that influence what evidence is available in product liability cases.EU AI Act – Regulation (EU) 2024/2803 – EUR‑Lex European Commission – AI Act overview European Parliament – AI Act legislative summary
Implementation Best Practices
1. Establish a product liability and cybersecurity governance program
- Create a cross‑functional product liability committee (legal, security, engineering, product, risk) responsible for compliance with Directive (EU) 2024/2853.
- Governance structures are recommended by compliance frameworks and EU guidance to manage cross‑cutting digital product obligations.Directive (EU) 2024/2853 – EUR‑Lex NIS2 Directive – EUR‑Lex [ENISA – Governance & risk management guidance](https://www.enisa.europa
Recent developments
- — This regulatory tracker says the directive extends strict liability to software, AI systems, and digital manufacturing files, including cybersecurity vulnerabilities and failure to supply updates. It reports that Member States must transpose the directive by 2026-12-09. (source)
- — The tracker summarizes the directive as modernizing EU product liability rules for software, digital files, and AI systems and says Member States have until 2026-12-09 to transpose it. It also notes that the new regime applies to products placed on the market or put into service after that date. (source)
- — Freshfields says the EU’s cyber and AI guidance is now practically relevant because liability under the revised Product Liability Directive will soon overlap with other new EU cyber rules. The article highlights the December 2026 application date as a key milestone for manufacturers in cybersecurity-sensitive sectors. (source)
- — This industry article notes that EU cyber rules are tightening and points to the Product Liability Directive as becoming relevant on 2026-12-09. It frames the directive as part of a broader package of compliance deadlines affecting product security and AI-related documentation. (source)
- — Although focused on the Cyber Resilience Act, this article underscores the broader cybersecurity compliance environment that will feed into product-liability risk. It emphasizes that reporting obligations begin on 2026-09-11, while the Product Liability Directive’s strict-liability era begins later in 2026. (source)
- — Industry commentary in this piece suggests companies are aligning product documentation and AI output controls with both the AI Act and Product Liability Directive. The main impact described is increased compliance pressure on cybersecurity and product teams ahead of the 2026-12-09 application date. (source)
- — Reed Smith describes the EU product liability regime as part of an emerging enforcement framework for cybersecurity and consumer IoT. It states that the revised Product Liability Directive takes effect on 2026-12-09 and sits alongside the EU Cyber Resilience Act and Data Act in the compliance timeline. (source)
- — Latham & Watkins explains that authorities and courts must now consider cybersecurity requirements when assessing whether a product is defective. The note also stresses that companies should prepare for the stricter liability standards that will apply by 2026-12-09. (source)
- — This commentary argues that missing security patches can now become a product-defect issue under the new directive. It also says software is explicitly treated as a product and that cybersecurity expectations are central to defect analysis. (source)
- — Gibson Dunn says the directive significantly expands Europe’s strict-liability regime to software-driven products, stand-alone software, and digital elements. It also warns that substantial modifications or updates after 2026-12-09 may bring older products into scope. (source)
Related regulations
- Artificial Intelligence Liability Directive — European Union, Active
- EU AI Act - Annex III High-Risk System Requirements (2 Dec 2027) — European Union, Upcoming, effective 2027-12-02
- EU Data Act — European Union, Phased, effective 2025-09-12
- EU Cyber Resilience Act (CRA) — European Union, Phased, effective 2027-12-11
- EU AI Act - GPAI Model Obligations (2 Aug 2025) and Enforcement (2 Aug 2026) — European Union, Active, effective 2025-08-02
- EU Digital Omnibus on AI (Regulation (EU) 2026/1744) — European Union, Active, effective 2026-07-27
- EU AI Act - Synthetic Media Transparency and New Prohibitions (2 Dec 2026) — European Union, Upcoming, effective 2026-12-02
- EU AI Act - Annex I High-Risk Systems (2 Aug 2028) — European Union, Upcoming, effective 2028-08-02
Put it into practice
- Generate the policy: GDPR policy generator (generatepolicy.com)
- Buy the policy pack: GDPR Complete Bundle (cyberpolicy.shop)
- Build it yourself: GDPR & DPIA Compliance Workbook (ciso.diy)
Browse all regulations · Compliance deadlines · Latest updates