← Back to the 100 Software Failures Timeline
Case Study #18 — Top 100 Software Failures

Medtronic MiniMed insulin pump cybersecurity recall

FDA-classified Class I (most serious) recall affecting roughly 4,000 insulin pumps in the US due to risk of over- or under-delivery of insulin.

2019-06-27
When it happened
Healthcare / Medical Devices
Sector
#18 of 100
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

FDA-classified Class I (most serious) recall affecting roughly 4,000 insulin pumps in the US due to risk of over- or under-delivery of insulin.

Healthcare
Sector affected
2019-06-27
Date of the event
#18
Rank in the Top 100 Software Failures
2
Distinct root-cause clauses identified below
02 — The Root Cause

What the software actually got wrong

The pump's wireless communication protocol lacked encryption/authentication, a design flaw that could allow unauthorized commands; issued as a preventive recall with no confirmed patient harm from exploitation.

01Root Cause

The pump's wireless communication protocol lacked encryption/authentication, a design...

What Happened

The pump's wireless communication protocol lacked encryption/authentication, a design flaw that could allow unauthorized commands

How Requs AI Catches This

Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.

02Root Cause

Issued as a preventive recall with no confirmed patient...

What Happened

issued as a preventive recall with no confirmed patient harm from exploitation

How Requs AI Catches This

Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.

03 — How This Gets Caught Before It Happens

Beyond code coverage and "shall" testing

Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.

Requs AI Edge Case

Surfaces this before code exists

Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.

Requs AI Software FMEA

Connects the failure mode to the hazard

Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.

Find the overlooked root causes before they ship.

Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.