Editorial illustration.
Editorial illustration.
Corporate Targets · Cyberattack · 33 of 60

The Dealership Was Open. Its Business System Was Not.

The CDK outage left auto retailers working around a shared software failure. Filings published in 2026 show the delayed accounting consequences—and how a vendor’s restoration milestone could arrive before a customer’s full recovery.

On July 5, 2024, Sonic Automotive could again use the basic functions of its dealer-management system. Other functions, customer-management software and connected applications were still unavailable. The showroom could be open while the systems supporting its work remained partly offline.

That divided condition appears in Sonic’s securities filing, more than two weeks after CDK Global notified customers that it had suspended systems following a cyber incident. The affected software supported sales, inventory and accounting. Sonic said slower vehicle sales were likely to have a material effect on its second-quarter results.

The attack was at the provider, but the interruption traveled to the businesses depending on it. Dealers did not need to lose their buildings or vehicles to lose some of their capacity to transact. A car on a lot is not a completed sale: the business also needs records, financing processes, customer information and accounting to move together.

CDK’s platform served more than 15,000 dealerships across North America, according to BleepingComputer’s July 1 reporting. The report described dealers reverting to pen and paper and customers unable to complete some purchases or service visits. That was the reach of a shared platform, not evidence that every one of those dealerships had closed its doors.

Workarounds provided continuity, but with limits. A process normally connecting several departments in one system had to be carried across alternative records and later reconciled. Being able to continue some work was different from operating at the previous speed.

The Vendor’s Milestone Was Not Every Customer’s Finish Line

On July 3, CDK’s owner, Brookfield Business Partners, announced that substantially all customers had returned to the core dealer-management system before the Independence Day weekend. Its statement also said other applications, including customer-management and service tools, were still being brought back.

The parent company did not expect a material impact on its own business. That assessment was made at the parent’s scale. It did not mean that the loss was immaterial to a dealer whose own transactions depended on CDK.

Sonic’s July 5 disclosure fits that distinction rather than contradicting the restoration announcement. Basic access had returned, while other capabilities remained under investigation and testing. A core platform could be running without every application connected to it being ready.

AutoNation later supplied a longer recovery sequence. In its 2025 annual report, filed in 2026, the company said core functions were restored by the end of June 2024. Ancillary systems and integrations followed by the end of July, with residual effects resolved by the end of the third quarter.

That sequence covered tools automating scheduling, ordering, payments, sales and reporting. It explains why a single “back online” date is too blunt a measure for a business assembled from interdependent applications. Access, automation and the clearing of residual disruption can arrive at different times.

The exposure also differed within corporate groups. Penske’s 2025 annual report said its American and international automotive dealerships did not use CDK’s dealer-management system. Its Premier Truck Group did, and was affected. A company name on an outage list therefore did not identify which of its businesses had lost which function.

The Insurance Arrived in Another Reporting Year

For Sonic, the financial account extended beyond technical restoration. Its 2025 annual filing, published in February 2026, estimated that the outage negatively affected reported pretax income by approximately $47.2 million during 2024. That included about $13.4 million in additional compensation expenses; the compensation was not a further amount to add on top.

The same disclosure recorded $10 million in pretax income from cyber-insurance proceeds in the final quarter of 2024 and $40 million during 2025. The proceeds reduced selling, general and administrative expenses. An operational shock in one year thus produced an accounting benefit in the next.

Those entries do not establish that the attack generated a profit. The estimated disruption effect and the insurance recognition are different accounting descriptions across periods, not a complete reconciliation of every loss, policy term or recovery. Nor can the insurance money recover each customer’s lost time or every employee’s disrupted workday.

The practical lesson is contained in the gap between the July announcements. The supplier could restore its core system while a dealer was still waiting for connected tools; a dealer could recognize insurance proceeds long after both had resumed work. What looked like one outage from a distance was a chain of separate recoveries, ending on different dates in different businesses.

Compiled November 16, 2026. Records and findings keep the dates stated in their sources; each link in the text opens the document it relies on.