BMW Recalls 286 i5 and i7 Cars Over Charging Software

Two hundred eighty-six BMW electric cars left production with the wrong battery charging software, and the company is calling them back to dealers for an update. The campaign entered the federal recall register on November 4, 2026, under number 26V731. It reaches the top of BMW's electric sedan range, the i5 and the i7, in their newest model years, and the fault sits in code rather than in any part an owner can see or touch.

The covered cars are specific, and there aren't many of them. The recall takes in certain 2027 i7 xDrive50 and i7 xDrive60 sedans, and certain 2026 and 2027 i5 xDrive40, i5 eDrive40 and i5 M60 cars. Five model variants, two nameplates, one shared piece of software. A wrong version reached a small slice of production, which is why the population stops at 286.

The consequence the notice names is not the usual fire language. NHTSA's record says software that doesn't charge the battery properly can lead to electric shock, increasing the risk of injury. The notice doesn't report any shock incidents, crashes or injuries tied to the campaign. It also doesn't describe a charging failure owners would notice at a plug, which is the awkward part: a car can carry this defect and behave normally in daily use.

The fix matches the fault. Dealers will update the high voltage battery charging software, free of charge. There's no part to order and no hardware to replace, so the repair is a service visit measured in software time rather than shop days. Owners can call BMW customer service at 1-800-525-7417 with questions about the campaign.

The paperwork runs on a holiday schedule. Owner notification letters are expected to be mailed on December 25, 2026, and the vehicle identification numbers in the campaign become searchable on NHTSA.gov the same day. Until then, an i5 or i7 owner who wants an answer has to ask a dealer, because the public VIN lookup can't confirm a specific car yet.

Recalls built on software have changed what a campaign looks like from the owner's side of the counter. There's no failed component to inspect, no wear pattern to photograph and no symptom to describe to a service adviser. The evidence is a version number on a build record, matched against a list. That makes early, narrow campaigns like this one more common: a maker can find exactly which cars received a given build, down to a population of 286, and leave every other car alone.

For the 286 owners, the practical read is simple. The car is under recall now, the remedy is free, and the letter that makes it official lands on December 25. A software update is the cheapest fix a manufacturer can ship, but it still needs the car in a service lane, and that's the step the December letters are there to trigger.

Small recalls like this one rarely make noise, and that's part of their value as a signal. A 286-car campaign means BMW caught a version mismatch early, in a production slice narrow enough to name by variant and model year. The alternative history, a wrong software version spread across a full model year, is the kind of campaign that runs to six figures and a year of letters. Owners of the five named variants should treat the December date as a start, not a deadline, and book the update when the letter arrives.