Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

MD HB712: Civil Actions - Product Liability - Artificial Intelligence Systems

Dead/Failed Maryland · 2026 session

Last verified Oct 10, 2026 · official bill text

HB712 · where it stands

This bill did not become law (dead/failed) · last action Feb 5, 2026.

What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

Maryland's HB 712 (2026, first reader text) would have added Courts and Judicial Proceedings sections 3-2701 to 3-2706 letting people sue developers and deployers of high-impact or generative AI systems for harm from a dangerous or defective product (design defect, failure to warn, express warranty), with comparative fault, joint and several liability, and Attorney General enforcement. It had a House Judiciary hearing set for February 25, 2026 and died when the 2026 session ended.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

None: the bill died and did not become law. It would have exposed developers and deployers of high-impact and generative AI to product liability claims and Attorney General suits.

Key provisions

  1. Product: a high-impact AI system or a generative AI system; deployer excludes an individual or small business with fewer than 20 employees or fewer than 10,000 users; peer-reviewed scientific research use is exempt
  2. Design defect: plaintiff must show failure to use reasonable care, knowledge of the defect, accounting for foreseeable uses, and a feasible alternative design
  3. Failure to warn and express warranty claims; defense to failure to warn if the user was at least 17 and the danger was known, should have been known, or open and obvious
  4. A deployer could be held liable in place of the developer if it made a material and substantial change to the product or intentionally misused it contrary to an express warranty
  5. Rebuttable presumption of non-defect for developers who test and validate per industry practice, mitigate and disclose risks, and for deployers with a documented risk management policy
  6. Attorney General may sue for injunctive relief, civil penalties and compensation, with 30 days' written notice before seeking an injunction; contributory negligence is no bar and it is no defense that the AI caused the harm autonomously
  7. Would have taken effect October 1, 2026

Latest legislative action

Feb 5, 2026. Hearing 2/25 at 1:00 p.m.; died when the Maryland General Assembly's 2026 session ended April 13, 2026

Sponsors (showing 5 of 50)

NameRole
Primary
Primary
Primary
Primary
Primary

Topics and industries

Related topics

Affected industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error