Hyundai Ioniq 9 power-seat software recall (26V588)
Hyundai recalled 5,360 2026 Ioniq 9 SUVs whose second-row power seats may keep moving after contacting a person, a recurrence of the Palisade defect, with two alleged minor injuries reported.
The damage was public. The root cause was preventable.
Hyundai recalled 5,360 2026 Ioniq 9 SUVs whose second-row power seats may keep moving after contacting a person, a recurrence of the Palisade defect, with two alleged minor injuries reported.
What the software actually got wrong
Hyundai attributes the problem to software governing the second-row power seats, which may not recognize an occupant or object in the way; dealers or an over-the-air update will install revised seat-controller logic.
Hyundai attributes the problem to software governing the second-row...
Hyundai attributes the problem to software governing the second-row power seats, which may not recognize an occupant or object in the way
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.
Dealers or an over-the-air update will install revised seat-controller...
dealers or an over-the-air update will install revised seat-controller logic
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.
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.
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.
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.