Product liability for software: what applies from December 2026
4 min read
The new Product Liability Directive (EU) 2024/2853 expressly covers software. A manufacturer who fails to provide security updates can no longer argue that the defect only arose after the sale. This guide summarises what the directive means for manufacturers of software and connected products.
From when and for what
The directive applies to products placed on the market or put into service after 9 December 2026. Member States must transpose it into national law by that date; the previous Product Liability Directive 85/374/EEC is repealed with effect from the same date and continues to apply to older products.
A product is any movable – expressly including software and digital manufacturing files, even where integrated into another movable. Free and open-source software that is developed or supplied outside the course of a commercial activity is not covered.
In court, the national transposition law is decisive. This guide describes the directive, not its transposition in individual Member States.
Source: Art. 2(1) and (2) Product Liability Directive · Art. 4, point 1 Product Liability Directive · Art. 21 Product Liability Directive · Art. 22 Product Liability Directive
Which damage is compensated
- Death or personal injury, including medically recognised damage to psychological health.
- Damage to or destruction of property – but not the defective product itself and not property used exclusively for professional purposes.
- New: destruction or corruption of data that are not used for professional purposes.
When a product is defective
A product is defective if it does not provide the safety that a person is entitled to expect or that is required under Union or national law. Account is taken, among other things, of the relevant product safety requirements, expressly including safety-relevant cybersecurity requirements, and of the reasonably foreseeable effect on the product of other products expected to be used together with it.
Where the manufacturer retains control over the product after placing it on the market, the relevant moment is when the product left the manufacturer’s control. The manufacturer has control, among other things, as long as it can supply software updates or upgrades itself or via a third party.
A product is not considered defective for the sole reason that a better product, or an update, has since become available.
Source: Art. 7 Product Liability Directive · Art. 4, point 5 Product Liability Directive · Recital 19 Product Liability Directive
Missing security updates
Until now, a manufacturer could be exempted if the defect probably came into being after the product was placed on the market. This exemption does not apply where the defectiveness is within the manufacturer’s control and is due to software, including updates, to a related service, to a substantial modification or to the lack of software updates or upgrades necessary to maintain safety.
The directive itself does not create an obligation to provide updates (Recital 51). For products with digital elements, that obligation follows from the Cyber Resilience Act: vulnerabilities must be addressed without delay during the support period, and security updates provided free of charge.
If the owner does not install updates that have been provided, this lies outside the manufacturer’s control; if the injured person negligently failed to install an update, liability can be reduced or disallowed. If a third party exploits a vulnerability, on the other hand, this does not reduce liability.
Source: Art. 11(1)(c) and (2) Product Liability Directive · Recital 51 Product Liability Directive · Art. 13 Product Liability Directive · Recital 55 Product Liability Directive · Art. 13(8) CRA · Annex I, Part II, points 2 and 8 CRA
Disclosure of evidence and burden of proof
In principle, the claimant proves the defectiveness, the damage and the causal link. Once the claimant has made the claim plausible, the court can order the defendant to disclose relevant evidence – limited to what is necessary and proportionate, with protection of trade secrets.
- Defectiveness is presumed if the defendant fails to disclose the requested evidence, if the product does not comply with mandatory product safety requirements intended to protect against the damage that occurred, or in the case of an obvious malfunction.
- Where technical complexity makes proof excessively difficult, it is sufficient for the claimant to show that defectiveness or the causal link is likely.
- The defendant can rebut any presumption.
Source: Art. 9 Product Liability Directive · Art. 10 Product Liability Directive
Who is liable
- The manufacturer of the defective product – also for defective components integrated under its control.
- The manufacturer of a defective component, where that component caused the product to be defective.
- For manufacturers outside the EU, additionally the importer, the authorised representative or the fulfilment service provider.
- Anyone who substantially modifies a product outside the manufacturer’s control and then makes it available is considered a manufacturer.
Where several persons are liable, they are jointly and severally liable. Liability towards the injured person can neither be limited nor excluded by contract.
Source: Art. 8 Product Liability Directive · Art. 12(1) Product Liability Directive · Art. 15 Product Liability Directive
Time limits
- Limitation period: three years from awareness of the damage, the defectiveness and the liable economic operator.
- Expiry period: ten years from placing on the market – in the case of a substantial modification, from when the modified product is made available again; 25 years for latent personal injury.
Source: Art. 16 Product Liability Directive · Art. 17 Product Liability Directive
In practice
- For each product and version, record traceably when a vulnerability became known, how it was assessed and when which update was available – this is the basis for being able to disclose evidence.
- Determine and keep to the support period under the Cyber Resilience Act; it determines how long security updates are expected.
- Inform users about updates and document how and when they were provided.
- Keep track of purchased components and their updates (SBOM) – defects in integrated components also affect the manufacturer of the end product.
- Keep records for at least the ten-year expiry period.
Related guides
Terms in the Cyber Resilience Act glossary
Sources
- Directive (EU) 2024/2853 (product liability), Art. 2, 4, 6–13, 15–17, 21, 22, Recitals 19, 51, 55 (EUR-Lex, Official Journal)
- Regulation (EU) 2024/2847 (Cyber Resilience Act), Art. 13(8), Annex I, Part II (EUR-Lex, Official Journal)
First published 20 Oct 2026, last updated 20 Oct 2026. This guide reflects the wording of the regulation and the Commission’s guidelines and does not constitute legal advice.