Pwn2Own Automotive 2026 exposes attack paths in EV and IVI interfaces

At a glance

What this is: This analysis of Pwn2Own Automotive 2026 shows how NFC, hardcoded credentials and USB interfaces can turn connected vehicle convenience features into exploitable entry points.

Why it matters: It matters because OEM, supplier and charge point teams need to treat contactless access, firmware trust and infotainment input handling as security boundaries, not usability features.

By the numbers:

• Pwn2Own Automotive 2026 produced 76 unique zero-day vulnerabilities across automotive technologies.

Context

Connected vehicle security now extends beyond the vehicle core to the interfaces that let people, devices and updates interact with it. NFC taps, USB ports and firmware update paths can all become security boundaries when they accept untrusted input or privileged actions without strong validation.

This post looks at what Pwn2Own Automotive 2026 revealed about that boundary problem. The event surfaced a practical attack surface in EV charging and infotainment systems, which is typical of modern automotive platforms where convenience, maintenance and operational control increasingly share the same trust model.

Key questions

Q: What breaks when a connected vehicle interface is trusted too broadly?

A: When a contactless or physical interface is trusted too broadly, untrusted input can reach parsing logic, maintenance functions or operational controls. That can turn a convenience feature into code execution, unauthorized configuration change or fleet-wide exposure. The failure is usually not one control alone, but a lack of validation, isolation and integrity checks across the same path.

Q: Why do hardcoded credentials increase risk in EV charging and infotainment systems?

A: Hardcoded credentials create the same access pattern across many devices, which means one leak or one reverse-engineered secret can expose repeated functions across a fleet. If those credentials also unlock updates or maintenance actions, the risk compounds. The result is identity debt built into firmware, with very limited room for containment once the secret is known.

Q: How do teams know whether embedded interface controls are actually working?

A: Teams should look for whether untrusted input is being rejected, whether privileged functions require unique credentials, and whether firmware or configuration content is blocked when integrity checks fail. If a contactless tap, USB device or shared secret can still reach operational logic, the controls are not working as intended. Evidence should show enforced separation, not just policy text.

Q: What should OEMs and suppliers do when zero-day research exposes a vehicle interface weakness?

A: They should prioritise containment over general patch planning. That means identifying affected models, checking whether the same interface pattern exists elsewhere in the fleet, and limiting exposure through segmentation, credential rotation and update validation before the issue spreads beyond a controlled research setting.

Technical breakdown

How NFC input becomes a code execution path in EV chargers

NFC is often treated as a convenience layer for pairing, payments or access control, but embedded systems still have to parse the data that arrives over it. When that parser contains memory-safety weaknesses, such as a stack-based buffer overflow, a simple tap can become a code execution path. The key issue is not NFC itself, but the decision to let user-controlled contactless input reach operational logic without enough input validation, memory protection or interface separation. In an EV charger, that can turn a convenience feature into a path that affects charging behaviour rather than just user interaction.

Practical implication: Treat contactless interfaces as attack surfaces and test their parsers with the same rigor you apply to network-facing code.

Why hardcoded credentials and weak update validation amplify charger risk

Hardcoded or shared credentials create a repeatable access pattern across embedded fleets, especially when maintenance, provisioning or update functions depend on the same secret. The risk rises when those functions also accept firmware, scripts or configuration packages without strong integrity checks. In that case, credential exposure is no longer just an authentication issue, it becomes a way to reach code execution or persistent device control. The article’s point is that access weakness and content-integrity weakness often compound each other. One opens the door, the other lets untrusted code stay inside the device.

Practical implication: Remove shared secrets from charger fleets and require cryptographic validation for every executable update path.

How USB-based infotainment compromise chains memory bugs into broader exposure

USB remains dangerous in automotive systems because it introduces untrusted data through a very familiar physical interface. The exploit pattern described here combines an information leak with an out-of-bounds write, which is a common way to make memory corruption reliable enough for exploitation. In practice, the port is not the real issue. The risk comes from parsers, OS-level protections and isolation boundaries inside the IVI stack. If those controls are weak, a removable device can become a straightforward path into infotainment compromise, with privacy and operational consequences even when safety-critical domains stay segmented.

Practical implication: Harden media parsers, enable exploit mitigations and isolate infotainment from more sensitive vehicle domains.

Threat narrative

Attacker objective: The attacker seeks reliable code execution or privileged device control over EV charging or infotainment systems.

1. Entry occurs through NFC, hardcoded credentials or a USB device that reaches trusted embedded parsing logic or administrative functions.
2. Escalation follows when memory-safety flaws, weak authentication or insufficient update validation let the attacker execute code or change device behaviour.
3. Impact is achieved through charger output manipulation, persistent device compromise or infotainment takeover that can affect availability, privacy or fleet-wide trust.

Breaches seen in the wild

• Commvault Metallic breach 2025: A nation-state actor exploited a Commvault zero-day in Azure and may have taken app secrets that open customers' Microsoft 365 tenants.
• Meta Muse agent hijack 2026: An undocumented Muse setting let local malware hijack Meta's personal AI agent, steal its authentication material and abuse user access.

Read and download The State of NHI & AI Agent Breach Report 2026, covering 200+ breaches impacting Non-Human Identities including AI Agents.

NHI Mgmt Group analysis

Convenience interfaces have become a first-class attack surface in connected vehicles. The article shows that NFC, USB and maintenance paths are not peripheral features once they can influence charging or infotainment behaviour. That matters because automotive programmes often inherit trust assumptions from consumer usability design rather than from hostile-input design. Security teams should treat every user-controlled interface as a governed entry point, not a benign accessory.

Hardcoded credentials create fleet-scale identity debt in embedded environments. In automotive infrastructure, a single shared secret can expose maintenance, provisioning and update functions across many deployed units, especially when rotation is difficult. That is an identity governance problem as much as a firmware problem, because access rights are embedded into device design and then replicated at scale. The governance gap is asset discovery and exposed interfaces without lifecycle control over the credentials that unlock them.

The real failure mode is not memory corruption alone, but the combination of untrusted input, weak validation and limited isolation. The article’s exploit patterns show how one defect rarely stays isolated in embedded systems. A parser bug becomes exploitable when the interface is reachable, and the impact widens when the affected component can reach operational control paths. Practitioners should read this as a control boundary problem, not just a bug-fix problem.

Automotive security programmes need to move from component thinking to interface governance. EVSE, IVI and connected vehicle ecosystems increasingly share trust boundaries across hardware, firmware and remote management. That makes vulnerability triage, update integrity and segmentation part of the same governance conversation. The organisations that keep treating these as separate workstreams will miss the cumulative risk, so practitioner teams should align asset, credential and interface governance under one control view.

Memory-safety findings remain operationally relevant because they expose where defensive assumptions still fail. Zero-day discovery here is useful not because it proves novelty, but because it reveals where exploitability remains practical in real systems. The right response is to look for repeatable conditions, shared credentials, weak validation and poor separation across the fleet. Security leaders should use those patterns to prioritise controls where compromise would scale fastest.

Read next: Zero-Day and Exploited Vulnerabilities Guide

What this signals

Interface governance is now a core automotive security discipline. Connected vehicle programmes cannot rely on the assumption that physical proximity or user convenience implies trust. The more an interface can influence charging, firmware or infotainment logic, the more it needs explicit validation and isolation as a managed control boundary.

Fleet-scale identity risk in embedded systems starts with reusable access paths. Hardcoded or default secrets in charging and vehicle systems behave like standing privilege, because they let the same access path survive across multiple devices and updates. Practitioners should treat secret reuse as an operational governance failure, not only a coding flaw.

Attack-surface discovery needs to include contactless and removable media paths. Automotive security teams should not focus only on remote services and telematics. NFC, USB and maintenance interfaces can be the shortest route to exploitable behaviour when they sit near privileged logic, so discovery and testing need to map those pathways explicitly.

For practitioners

• Harden NFC input paths Apply the same validation standards to contactless input that you require for network-facing interfaces, and test embedded parsers for overflow and malformed input handling.
• Eliminate shared maintenance credentials Replace hardcoded, default or reused secrets with unique, revocable credentials for provisioning and service operations across the charger fleet.
• Require integrity checks for all executable content Reject firmware, scripts and configuration packages unless the device can cryptographically verify their origin and integrity before execution.
• Isolate convenience interfaces from control logic Separate contactless, USB and other user-facing interfaces from charging output and operational controls so a compromise cannot directly alter device behaviour.
• Harden infotainment parser and memory controls Use fuzzing, ASLR, DEP or NX, stack canaries and control flow integrity to make USB-delivered content harder to turn into reliable execution.

Key takeaways

• Connected vehicle risk now extends to interfaces that were originally designed for convenience, including NFC taps, USB media and maintenance paths.
• The article’s evidence links zero-day discovery to repeatable failure patterns such as hardcoded credentials, weak validation and poor isolation.
• OEMs, suppliers and charge point operators need to govern these interfaces as attack surfaces and verify that trust boundaries still hold under hostile input.

Related NHI Mgmt Group resources: Zero-Day and Exploited Vulnerabilities Guide · Attack Surface Management Guide · Automotive Cybersecurity Guide · OWASP Agentic Applications Top 10

Key terms

• XML Parser Hardening: XML parser hardening is the practice of configuring parsing libraries so untrusted XML cannot resolve external entities or trigger uncontrolled expansion. In practice, that means using safe defaults, limiting document complexity, and testing parser behavior against malicious inputs. The goal is to preserve availability and prevent unintended data access.
• Hardcoded Credential: A secret such as a password, API key, or token embedded directly in source code rather than retrieved from a secure vault at runtime. Hardcoded credentials are one of the most common and dangerous NHI vulnerabilities.
• Interface isolation: A control design that prevents one exposed interface from directly influencing sensitive internal functions. In connected vehicles, isolation limits the blast radius of a compromised NFC, USB or maintenance path by separating convenience features from operational control and safety-relevant logic.

Deepen your knowledge

NHI Mgmt Group covers identity security, NHI governance, and agentic AI through independent research, practitioner guides, and the NHI Foundation Level course. Explore nhimg.org for resources that connect identity governance to the broader security disciplines your programme depends on.