Austria has published a draft Product Liability Act 2026 to implement the EU Product Liability Directive, with a proposed start date of 9 December 2026 for products placed on the market or put into service from then; consultation was open until 12 November 2026. The draft, which would replace Austria’s 1988 law, brings software and AI systems, digital manufacturing files and related services within product liability, while extending potential liability to parties such as component manufacturers, importers and some online platforms. It broadens recoverable damages, provides for court-ordered evidence disclosure and eases proof for injured persons through rebuttable presumptions. The draft also links liability to cybersecurity requirements, including failures to provide safety updates.
Austria published a draft implementing Act (Produkthaftungsgesetz 2026 – “PHG 2026”) for the EU Product Liability Directive ((EU) 2024/2853, shortly “PLD”). The draft confirms the Directive’s transposition deadline of 9 December 2026 as the entry into force date in Austria for products placed on the market or put into service from that date.
The draft Act closely follows the Directive. It aims to adapt product liability law to technical and economic developments, makes it easier for injured persons to enforce compensation claims and follows a maximum harmonisation approach.
Consultation was open until 12 November 2026. If enacted, the draft would replace the PHG of 1988, which has governed product liability in Austria for almost four decades.
The draft PHG 2026 aims to adapt product liability law to technical and economic developments and makes it easier for injured persons to enforce compensation claims. As the PLD follows a maximum-harmonisation approach, the draft PHG 2026 stays close to the Directive. It proposes entry into force on 9 December 2026 and application to products placed on the market or put into service from that date; earlier products would remain subject to the current PHG.
1. Software and digital manufacturing files as “products”
The revised definition of “product” expressly includes raw materials, digital manufacturing files (e.g. templates for 3D printers) and software, alongside movable goods and electricity. The term “software” is deliberately left undefined to accommodate future technical developments.
Software, including AI systems, is covered regardless of whether it is stored on a device, accessed via the cloud or provided as SaaS. Digital services integrated into or connected with a product where the product could not perform one or more of its functions without them (“related services”) qualify as components. Free and open-source software developed or supplied outside a commercial activity is excluded, but manufacturers that commercially integrate it into their products may still be liable for damage caused by defects in that software.
2. Liability beyond market placement
Manufacturers may also remain liable after a product is placed on the market or put into service. Where defects stem from a related service, software (including updates or upgrades), missing software updates or upgrades needed to maintain safety, or a substantial modification, the “later defect” defence is unavailable if the relevant cause is within the manufacturer’s control.
3. Liability for modified products
Reflecting the principles of the circular economy, a person who substantially modifies a product outside the manufacturer’s control and subsequently makes it available on the market or puts it into service is treated as a manufacturer. This is particularly relevant to refurbishers and “upcycling” businesses.
4. More liable economic operators
The manufacturer remains the primary addressee of claims, but the circle of liable parties is broadened. Component manufacturers are liable where a defective component was integrated into or connected with a product under the product manufacturer’s control and caused that product to be defective. If the manufacturer of a product or component is based outside the EU, the importer and the manufacturer’s authorised representative are additionally liable; the so-called “fulfilment service provider” within the meaning of Section 2(13), which provides at least two of the specified services, including warehousing, packaging, addressing or dispatching, in the course of a commercial activity is liable if there is no EU-based importer and no authorised representative. Where no liable EU-based operator can be identified, suppliers and, subject to specific further preconditions, online platforms are liable if they fail to identify such an operator or their own supplier within one month of receiving a request.
5. Wider scope of recoverable damage
The draft PHG 2026 covers damage suffered by natural persons. Recoverable damage expressly includes medically recognised harm to psychological health and the destruction or corruption of data not used for professional purposes. Mixed-use property is covered, but not the defective product itself or a product damaged by a defective component integrated into or connected with it by or under the control of that product’s manufacturer. Property used exclusively for professional purposes remains excluded, and the EUR 500 deductible for property damage is abolished.
6. Disclosure of evidence
Courts may order disclosure of relevant evidence in the opponent’s control where necessary and proportionate. A claimant seeking disclosure must present a plausible claim; a defendant must substantiate its need for evidence for its defence. Courts may require evidence to be presented in an easily accessible and understandable form and must take measures to protect trade secrets.
7. Easier proof for injured persons
The claimant generally bears the burden of proving damage, defectiveness and causation. Defectiveness is presumed if the defendant fails to disclose relevant evidence as required under § 6, the claimant proves non-compliance with binding safety requirements intended to protect against the risk of the damage suffered, or the claimant proves that an obvious malfunction caused the damage during reasonably foreseeable use or under ordinary circumstances. Causation is presumed once defectiveness is established and the damage is of a kind typically caused by that defect. If, despite disclosure and considering all relevant circumstances, proof is excessively difficult, particularly because of technical or scientific complexity, showing that defectiveness, causation or both are likely sufficing. All presumptions and assumptions remain rebuttable.
8. Interplay with the Cyber Resilience Act
The PHG 2026 should not be read in isolation. The EU Cyber Resilience Act (Regulation (EU) 2024/2847 – “CRA”) describes itself as complementary to the PLD: while the CRA sets out mandatory cybersecurity requirements for products with digital elements, the PLD provides the liability consequences where a lack of safety, including missing security updates, causes damage. In practice, the two regimes interlock in three ways:
- CRA requirements as a liability benchmark: under the draft, defectiveness is assessed by reference to applicable product safety requirements, including safety-relevant cybersecurity requirements, and is presumed where mandatory safety requirements intended to protect against the risk of the damage suffered are breached. Non-compliance with the CRA’s essential cybersecurity requirements (e.g. no known exploitable vulnerabilities, secure-by-default configuration) may therefore become the starting point of a product liability claim.
- Security updates: the CRA obliges manufacturers to handle vulnerabilities and provide free security updates for a support period of generally at least five years. The draft PHG 2026, in turn, denies manufacturers the “later defect” defence where damage results from a lack of security updates within their control.
- Documentation as evidence: technical documentation, cybersecurity risk assessments and vulnerability records may be subject to disclosure where relevant to the claim or defence and where disclosure is necessary and proportionate, subject to the draft’s trade secret protections.
Timing matters: the CRA’s reporting obligations for actively exploited vulnerabilities and severe incidents (Art. 14) have applied since 11 September 2026, and its rules on notification of conformity assessment bodies (Chapter IV) since 11 June 2026; the remaining obligations apply from 11 December 2027 – i.e. one year after the PHG 2026 is set to take effect.
9. Our take
Companies developing, integrating, updating or distributing software, AI systems or products with digital elements should assess their exposure now. Although the draft may see some changes in the legislative process, the core provisions are unlikely to change and the envisaged entry into force deadline is fast approaching.
We recommend manufacturers and traders of not purely analogue consumer products start auditing product portfolios, reviewing update and cybersecurity processes, preparing documentation for potential disclosure requests, revisiting liability allocation in supply and development contracts (bearing in mind that liability towards injured persons cannot be excluded or limited in advance), and checking insurance coverage.
We will keep you informed as the legislative process progresses and are happy to discuss what the new rules mean for your business.
https://www.wolftheiss.com/insights/austrias-draft-product-liability-act-2026-software-and-ai-move-into-strict-liability