社会ガイド

The EU Revised Product Liability Directive and Software

Directive (EU) 2024/2853 expressly treats software, including AI systems, as a product for no-fault product-liability rules.

3 分で読めます
最終更新日 2026年9月26日

読み始めるクイズに答えてください

このページでは3 分で読めます

概要
ディープダイブ
戦略的影響
The Future of The EU Revised Product Liability Directive and Software
現実世界の実装
リスクとガードレール
実装ロードマップ
探検を続けましょう
よくある質問

概要

It applies to products placed on the market or put into service after 9 December 2026; claimants still need to establish damage, defect, and causation, subject to the Directive’s evidence and presumptions framework.

ディープダイブ

The revised Product Liability Directive updates EU strict-liability rules for defective products. It clarifies that software is a product whether installed on a device, accessed over a network, or supplied through cloud or software-as-a-service delivery. Developers and producers of software, including AI system providers within the AI Act definition, can be treated as manufacturers. The Directive also addresses software updates, upgrades, and related services that affect product safety. No-fault liability does not mean automatic liability for every AI error. A claimant must prove damage, a defect, and a causal link, though the Directive adds disclosure duties and rebuttable presumptions for certain circumstances that make proof excessively difficult or where non-compliance or obvious malfunction is shown. Defectiveness considers safety a person is entitled to expect or that is required by EU or national law, including presentation, reasonably foreseeable use, product characteristics, and the time it was placed on the market. A system’s compliance paperwork is relevant evidence but does not by itself decide defectiveness. Covered damage includes death, personal injury, certain property damage, and destruction or corruption of data not used for professional purposes. The Directive excludes the content of digital files and mere source code as products. Free and open-source software developed or supplied outside a commercial activity is excluded, while commercial supply, paid support, or other circumstances need careful analysis. The new rules apply only to products placed on the market or put into service after 9 December 2026; the prior Directive continues for earlier products. The Directive does not replace contract, negligence, data-protection, or AI Act duties. Businesses should preserve version, update, warning, testing, and incident evidence, map manufacturer and component-provider roles, and review supply contracts. National transposition and case law will determine practical details; assess the relevant Member State and product timeline.

技術的な洞察

A software liability file should preserve the version supplied, release and update dates, intended and foreseeable uses, safety notices, testing, and incident records. Track who controlled an update and whether it changed a safety-relevant feature. These records help distinguish the product supplied from later configurations. Article 10 does not make technical complexity alone sufficient for a presumption. For its excessive-difficulty route, the court considers the circumstances and the claimant must also demonstrate the specified likelihood of defectiveness or causation. Other presumptions have different triggers, including failure to disclose relevant evidence or an obvious malfunction under the stated conditions. Separate the claimed damage from the technical error. A wrong output is not itself proof of a covered injury or causal link. Cloud delivery does not automatically put software outside scope, while professional data loss is outside the specified non-professional data-damage category.

戦略的影響

リスクと安全性

AI による壊滅的な被害も日常的な被害も、誰がリスクを理解し、誰が行動できるかにかかっています。

より明確な判決

国民と専門家のリテラシーは、強力な安全政策が政治的に可能かどうかを左右します。

誇大広告を打ち破る

明確な説明は、誇大広告、研究室の PR、曖昧な倫理劇場に囚われることを減らします。

The Future of The EU Revised Product Liability Directive and Software

Member States must transpose the Directive by 9 December 2026, and its product scope uses the date of market placement or putting into service. National implementation and later decisions will shape how software evidence, presumptions, and covered damage are handled in practice. Keep a dated record of the relevant national law and the product’s release history. Review customer notices, incident preservation and supplier responsibilities against the actual product and jurisdiction. Treat a claim as a fact-specific assessment rather than assuming that every model error either creates liability or falls outside it.

現実世界の実装

A company provides an AI decision system as SaaS and assesses it as software under the Directive.

An update changes model behavior, so the manufacturer preserves version and safety-test records.

A consumer’s personal photos are corrupted by defective software, and the parties examine the Directive’s damage conditions.

A nonprofit releases open-source code outside commercial activity and checks whether the exclusion applies to the facts.

リスクとガードレール

能力が複雑になる一方で、実存的なリスクを SF として扱います。
高度な自律性の下での調整による表面製品の安全性を混乱させる。
英語以外や専門家ではない聴衆には、低品質の情報源しか提供されません。

実装ロードマップ

製品の危害、誤使用、制御不能/調整不良のリスクを分離します。
どのような証拠がタイムラインと重大度についてのあなたの見方を変えるかを尋ねてください。
マーケティング上の主張よりも、一次情報源と具体的な評価を優先します。
意識だけでなく、キャリア、政策、資金、スキルなど、行動経路を 1 つ特定します。

探検を続けましょう

Free newsletter

Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.

One email each weekday. Unsubscribe in one click. We never sell or share your address.

Test yourself

Take the The EU Revised Product Liability Directive and Software quiz

Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.

クイズを開始する

Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation

よくある質問

What is The EU Revised Product Liability Directive and Software?

Directive (EU) 2024/2853 expressly treats software, including AI systems, as a product for no-fault product-liability rules. It applies to products placed on the market or put into service after 9 December 2026; claimants still need to establish damage, defect, and causation, subject to the Directive’s evidence and presumptions framework.

Does the Directive cover software delivered through SaaS?

The Directive covers software regardless of supply or usage mode.

What must a claimant generally establish?

The Directive uses strict liability but retains elements to prove.

Which item does the Directive exclude as a product?

The Directive distinguishes software from information content and source code itself.

Which open-source software may be excluded?

The exclusion is limited by its commercial-activity condition.

What evidence should a software manufacturer preserve?

These records help establish product behavior and safety over time.

学び続ける