Level 1. Deviation
LG Munich I: Google ordered to pay for false statements in AI summaries
- Developer
- Not established
- Model
- Not established
- When it happened
- May 28, 2026
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by heise.de. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 1 of 5Deviation
- Potential
- 1 of 5Deviation
The system behaved contrary to its instructions, and it stayed contained. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
Every record starts at level 1. No fact in the sources raised it.
What is established, and what is not
No structured facts are recorded for this one yet.
Where this came from
The original report · read September 20, 2026
LG Munich I: Google ordered to pay for false statements in AI summariesA structured incident database · read September 19, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it
A German court held Google directly liable for false claims generated by its AI OverviewsWhere we first saw it
Google Handed AI Liability Blow in German Ruling That Could Transform AI Search
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.