Editorial correction — November 11, 2026: An earlier version of this report implied that researcher David Schütz had hacked a Tesla Model 3 or demonstrated control of a live vehicle. His March 23 write-up instead described a successfully booted salvaged computer and touchscreen on a desk—an important starting point for security research, not proof of an exploitable vehicle vulnerability. We have corrected the chronology, component prices and technical claims without changing the original March 27 publication date.
What did David Schütz actually accomplish?
In March 2026, independent security researcher David Schütz documented how he assembled a functioning Tesla Model 3 in-car computer system out of components salvaged from damaged cars. His stated aim was to establish a controlled test platform for research under Tesla's bug-bounty program, where he could inspect the operating system and network interfaces without relying on a fully operational vehicle.
The achievement was real: with the correct power supply, touchscreen and cabling, the system booted and displayed Tesla's own user interface. But a working electronics setup is not a successful remote hack, and the published March report does not establish access to steering, braking or other safety-critical vehicle controls.
The best primary source is Schütz's original technical account dated March 23, 2026. It includes photographs and his actual sequence of errors, repairs and discoveries. This article summarizes the outcome and its significance rather than reproducing his experiment as a step-by-step exploitation tutorial.
What hardware was on the desk?
Tesla Model 3's relevant computer unit integrates the Media Control Unit (MCU) with the Autopilot computer (AP) in a shared assembly, normally situated toward the passenger side of the dashboard. Schütz bought a used main unit from the salvage market, together with a separate display and other components needed to power the assembly.
The researcher reported that salvaged Model 3 MCU assemblies were commonly listed for about $200–$300 when he searched. Crucially, the frequently repeated $175 figure was for the used touchscreen he purchased, not the main computer. Our original story assigned that price to the wrong part.
He also obtained an adjustable bench power supply capable of providing 12 volts, rather than powering the hardware from an intact Tesla vehicle. His account notes that the complete setup could draw up to approximately 8 amperes at peak load.
A salvaged computer is useful for debugging because it can be inspected without risking a functioning vehicle. It also brings uncertainty: disconnected harnesses may be incomplete, wires are often cut by salvage yards, and the hardware might have suffered damage before being removed.
Why did the display connection become the biggest obstacle?
The touchscreen required a specific multi-pin Rosenberger connector. Schütz consulted Tesla's public Electrical Reference documentation to identify the interface and its corresponding parts. He initially considered an automotive BMW-style LVDS cable because its appearance suggested it might match.
It did not fit the required connector. When he attempted an improvised connection between cut cable ends, the arrangement briefly operated before tiny wiring debris damaged a power-management component on the computer's board. That was an accident during bench assembly, not a deliberate bypass of Tesla software security.
A friend helped identify the damaged part as a MAX16932 step-down power controller. Schütz documented taking the board to a PCB repair shop for component replacement; by then, he had also purchased another salvage computer so the project could continue.
These details matter because the March report is a hardware integration story, not a record of vulnerabilities being exploited against a customer car.
The $80 wiring harness solved the display problem
Eventually, the researcher purchased an entire Model 3 dashboard wiring harness, rather than continuing to hunt for an individual display cable. He said the harness cost $80 and contained the necessary connectors because automotive wiring is bundled into larger looms.
Once he connected the harness, the Tesla computer and touchscreen started together and ran the car's operating system on his desk. That outcome meant the screen and main unit could communicate in a controlled setting. It did not turn the bench rig into a functioning automobile.
The exact wiring, connector and troubleshooting details are in Schütz's original post. Anyone working with powered electronics should follow appropriate electrical-safety procedures and the manufacturer documentation; a shorted board and a damaged power controller were real setbacks in this case.
What did the researcher find on the internal network?
With the computer powered, Schütz inspected network-facing services that could be useful for later authorized security testing. He described observing an SSH service as well as a REST-style diagnostic interface associated with Tesla's ODIN system.
The presence of an SSH endpoint did not mean he had successfully logged in as an administrator. His report says that SSH access required specially signed keys associated with Tesla. The ODIN interface was designed to work with diagnostic tools. Discovering a service and exploiting it are distinct research stages.
Similarly, being able to see a computer's CAN-related architecture on a test bench is not evidence that a remote attacker can send dangerous commands to a production vehicle. Any claim about bypassing authentication, remotely controlling car functions or extracting protected firmware would require separate research demonstrating those actions.
The original GameLogNews article speculated about possible access to steering, braking and battery systems. Those scenarios are no longer presented as actual discoveries or inevitable outcomes.
Why is this useful to security researchers?
Salvage-based test platforms can reduce the cost of legitimate security investigation. In cybersecurity, isolated hardware is valuable for studying software behavior, diagnostics, network boundaries and failure modes without placing a working car or its occupants at risk.
Tesla maintains a bug-bounty program for eligible security reports. That provides a framework for responsible disclosure. A standalone lab system can help a researcher prepare to identify and report issues, but its existence is not itself evidence that Tesla has a new security flaw.
An additional lesson is about reporting accurately. Readers should distinguish a board booting, a diagnostic interface being visible, an authenticated login, a verified exploit and remote vehicle control. Each step has different requirements and safety implications. Combining them under a sensational headline makes the technical achievement harder to understand.
Did this discovery reveal that Teslas can be remotely hacked?
Not in the documented March 2026 experiment. Schütz's own account concludes by listing future ideas such as exploring the user interface, network services, vehicle buses and perhaps firmware extraction. Those were research goals, not completed exploits reported in this article.
No vehicle-takeover demonstration, newly discovered remote-code-execution vulnerability, patch advisory or demonstrated access to live safety systems is established by the primary source. Readers should not infer one from a photo showing the Tesla display on a desk.
Frequently asked questions
Did a researcher hack a Tesla Model 3?
He successfully booted a salvaged Model 3 computer and touchscreen and explored some exposed lab interfaces. The cited report did not show a takeover of a complete vehicle.
Did the Tesla computer cost $175?
No. $175 was the price of the used touchscreen. Salvaged computer units in his search were generally listed around $200–$300.
Why was an $80 wiring harness necessary?
The correct display connector was difficult to purchase separately. A complete dashboard loom supplied the needed wiring in one assembly.
Was the Tesla operating system running on a laptop?
No. The original Tesla hardware was powered on the desk. A separate laptop helped the researcher inspect its network interface.
Is there a verified Tesla security vulnerability in this report?
Not a new exploit. The account provides a practical hardware research platform and notes services that could be investigated further.
Sources and photo credit
Primary source: David Schütz, March 23, 2026: Running Tesla Model 3's Computer on My Desk Using Parts From Crashed Cars. Secondary context: PC Gamer's March 2026 coverage. The original researcher retains credit for his independent work; GameLogNews did not perform these tests.
Hero photo: Steve Jurvetson, Tesla Autopilot HW2.5 and Infotainment Boards, photograph taken February 12, 2021, Wikimedia Commons, licensed Creative Commons BY 2.0. Unmodified photograph of a different Model 3 hardware assembly, not the exact board or desk arrangement used by Schütz. It shows the real physical infotainment and Autopilot circuit boards discussed in this report.
.jpg){kind=link}