BMW Says Test Software May Have Shipped in Recalled i5/i7 Charging Ports

Its November 4 filing identifies 286 potentially affected cars in two narrow build groups, a manufacturer-estimated 0.2% defect share and a free dealer software remedy.

This report reflects information available at publication or its last update; circumstances may have changed since then.

More EV Ownership coverage →

BMW's November 4, 2026 federal safety-recall report says its investigation of high-voltage charging-port components found that some units may have shipped with testing software instead of production software. The manufacturer describes that possibility in a filing covering 286 potentially involved BMW i5 and i7 EVs—not 286 vehicles confirmed to have defective software.1

The distinction is more specific than the “incorrect software” descriptions in several published recall summaries of NHTSA campaign 26V731. BMW's original report says its supplier alerted it on October 8; after an engineering investigation and review of supplier production and shipping records, BMW identified the potential test-versus-production software issue and decided on a voluntary recall October 28. The report establishes BMW's account of what might have been shipped, not a diagnosis for any particular car.12

Which BMW i5 and i7 cars are potentially involved?

BMW's filing breaks the 286-vehicle recall population into two specific groups:

Model and trims Model years Production dates Potentially involved
BMW i5 eDrive40, xDrive40, M60 2026–27 May 12–July 22, 2026 236
BMW i7 50xDrive, 60xDrive 2027 June 15–July 23, 2026 50
Total 286

BMW-reported production ranges and potentially affected counts in the November 4 NHTSA filing. A matching model and year does not establish that an individual VIN is included.1

BMW separately estimates that 0.2% of the potentially involved population actually has the defect. That is the automaker's estimated defective share, not a measured number of faulty cars and not the probability of an electric shock. Rounding the percentage into a supposed count of confirmed bad charging ports would misrepresent the filing.1

What BMW says the software issue could cause

The report says software that does not conform to the high-voltage charging specifications could increase the risk of electric shock or injury in rare cases. BMW reported no known related accidents or injuries as of its November 4 filing. Neither statement proves a shock occurred, rules out later reports, or confirms that test software reached a specific vehicle.1

BMW identifies TE Connectivity Solutions GmbH as the component manufacturer. Naming a supplier and describing the review of shipping records does not establish negligence, deliberate conduct or responsibility for any actual injury. The filing's “Do Not Drive” and “Park Outside” advisory boxes are unchecked; that is not a personalized assurance about a car's condition or permission to ignore vehicle warnings.1

What owners can check, and when BMW plans the fix

BMW's reported remedy is a free vehicle-software update at an authorized BMW dealership. Its November 4 filing lists dealer notification for November 4 and December 25, 2026 as the planned date for owner letters and VIN-searchable recall information. Those are reported schedule entries, not proof that letters have been mailed, a specific car has been repaired, or a dealer has already completed the update.1

Owners can check an individual vehicle using the NHTSA VIN recall search. NHTSA warns that VIN lists for some newly announced recalls may not yet be complete, so a missing early search result should not be treated as final proof that a vehicle is outside this campaign. Vehicle-specific eligibility and service arrangements should be confirmed through BMW or an authorized dealer.3

At The Charger's EV Recall Lookup provides a separate model-and-year view of NHTSA recall data. It is not a VIN-specific repair-status check, and a model-year match cannot establish whether an owner's car has the charging-port issue.4

Sources

Footnotes

  1. BMW of North America, November 4, 2026, original Part 573 Safety Recall Report, NHTSA campaign 26V731. Manufacturer-submitted federal record for the two production cohorts, potential population, 0.2% estimated defect share, supplier-record/testing-software account, possible risk, no-known-injuries statement as of filing, planned remedy/notification dates and advisory checkboxes. BMW's causal account is a qualified manufacturer statement, not independent proof for a given vehicle. ↩ ↩2 ↩3 ↩4 ↩5 ↩6 ↩7

  2. AnyRecalls, OEMDTC and Recall Weekly, 26V731 summary, OEMDTC listing, and Recall Weekly listing, indexed November 9–13 and checked November 15, 2026. These sampled summaries repeat general recall details but do not show the complete BMW supplier-record testing-software chronology in the versions examined; the observation is limited to these pages. ↩

  3. National Highway Traffic Safety Administration, Check for Recalls / VIN lookup guidance, checked November 15, 2026. NHTSA explains the purpose of VIN checks and that recently announced campaigns can have incomplete VIN data. This does not independently establish which BMW VINs are currently searchable. ↩

  4. At The Charger, EV Recall Lookup, checked November 15, 2026. Existing model/year data tool, not an official VIN-specific repair or eligibility determination. ↩