Automotive cyber risk shifted toward in-vehicle systems in Q3 2026

At a glance

What this is: VicOne's quarterly report shows automotive cyber risk remains broad, but in-vehicle systems overtook enterprise IT as the most affected domain in Q3 2026.

Why it matters: For IAM, PAM, NHI and adjacent security teams, the report matters because connected vehicles, fleet platforms, charging systems and enterprise agents now share attack paths that can cross identity, API and operational boundaries.

By the numbers:

• VicOne observed 400 automotive cybersecurity incidents in Q3 2026, down 16.1% from 477 in Q2.
• In-vehicle systems became the most affected domain with 174 incidents, compared with 149 affecting Enterprise IT.
• Asia increased 36.8% to 93 incidents, while the Americas accounted for 184 incidents.
• VicOne observed 97 automotive-sector ransomware incidents in Q3 2026.

Context

Automotive cybersecurity is no longer just an in-vehicle problem. As vehicles, charging infrastructure, fleet platforms, supplier environments, and enterprise workflows become more connected, the security boundary shifts from a single product to a multi-organisation control plane that depends on identity, access control, and trusted software delivery.

VicOne's Q3 2026 report shows that the dominant exposure moved closer to vehicle operation while ransomware, API weakness, and AI-related abuse continued across the wider mobility stack. For security leaders, that means governance has to span service accounts, third-party access, connected APIs, and operational technology touchpoints, not just traditional enterprise controls.

That pattern is typical of modern mobility environments: the weakest link is often not the vehicle alone, but the systems and identities surrounding it.

Key questions

Q: What breaks when connected vehicle systems rely on weak authentication and relayable trust?

A: Weak authentication lets attackers convert a small exposed surface into account takeover, telemetry access, or operational control. In connected mobility, the failure is usually not a single compromised host. It is a trust chain that accepts callers, sessions, or devices without enough proof, allowing the attacker to move from access to impact.

Q: Why do fleet platforms and charging systems create a larger security risk than isolated vehicle software?

A: Because they extend the trust boundary beyond the vehicle itself. Fleet tools, charging networks, supplier portals, and backend APIs often share identity, session, or integration assumptions. When those assumptions fail, an attacker can pivot into operational workflows, not just data systems, which increases both blast radius and recovery complexity.

Q: What are the signs that connected automotive access controls are failing?

A: Look for unauthenticated endpoints, replayable protocol flows, shared credentials across partners, excessive API reach, and AI or automation tools with broad service access. Those signals show that the environment is granting authority too easily or too widely, which is exactly when lateral movement and misuse become practical.

Q: How should organisations govern AI agents and third-party services in automotive workflows?

A: They should treat both as delegated actors with scoped privileges, explicit ownership, and periodic review. The key is to bind access to the task, the session, and the service identity, then remove standing authority wherever possible. That reduces the chance that automation or suppliers can turn routine integration into uncontrolled access.

Technical breakdown

Why connected vehicle ecosystems widen the attack surface

Connected mobility systems distribute trust across vehicle software, backend services, mobile apps, charging infrastructure, suppliers, and enterprise platforms. That means a weakness in one layer can propagate into another through APIs, update chains, remote access paths, or shared credentials. In practice, the control problem is not just vulnerability management but trust propagation across multiple operational domains. Automotive security therefore depends on understanding where identity, authentication, and software integrity boundaries actually sit, then verifying that each boundary is enforced consistently.

Practical implication: Map each connected service to its authentication, authorization, and update trust points before the next release cycle.

How unauthenticated APIs and relay paths become operational risk

The report highlights a recurring pattern: when a service exposes weak API authentication, relayable protocol handshakes, or insufficient access checks, attackers can move from logical access to operational impact. In automotive environments, that can mean account takeover, telemetry exposure, or indirect control of charging and vehicle functions. The technical issue is not simply that an API exists, but that the trust model assumes callers are legitimate without enough proof, binding, or session integrity. Once that assumption breaks, downstream systems often inherit the failure.

Practical implication: Review every externally reachable API and protocol handshake for proof of caller identity, replay resistance, and access scope.

Why AI and software supply chains now matter to automotive security

VicOne's findings show AI-related abuse in vehicle systems, manufacturing workflows, and enterprise agents, alongside malware distributed through legitimate update chains. That combination is important because it blends model or agent misuse with classic software integrity issues. A compromised or over-permissioned AI workflow can trigger unauthorized actions, while an untrusted update path can turn a legitimate distribution channel into a malware delivery mechanism. Automotive security teams have to treat AI permissions, build provenance, and update integrity as linked controls, not separate problems.

Practical implication: Tie AI permissions and software update assurance into the same governance review for connected automotive services.

Threat narrative

Attacker objective: The objective is to convert weak trust in connected automotive services into operational access, data exposure, or control over vehicle-adjacent systems.

1. Entry occurs through weak external trust boundaries such as unauthenticated APIs, relayable authentication flows, exposed telematics systems, or compromised update chains.
2. Credential or session abuse then enables account takeover, unauthorized service access, or control of fleet, charging, or enterprise workflows.
3. From there, attackers can pivot into vehicle functions, telemetry access, malware delivery, or downstream fraud and operational disruption.

Breaches seen in the wild

• Sisense breach 2024: A credential in Sisense's GitLab reportedly opened S3 buckets of customer tokens, passwords and certificates; CISA urged a full reset.
• CISA Private-CISA GitHub leak 2026: A CISA contractor's public GitHub repo exposed AWS GovCloud admin keys, Artifactory credentials and plaintext passwords for six months.

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

Automotive cyber risk is now a governance problem across connected identities, not a vehicle-only engineering issue. The report shows that the highest-risk paths span APIs, suppliers, charging systems, AI workflows, and update channels. That means ownership must extend beyond product security into identity governance, access control, and third-party lifecycle oversight. Practitioners should manage the vehicle ecosystem as a distributed trust environment.

Unauthenticated and replayable access patterns are the decisive failure mode in connected mobility. The article's examples point to a trust model that accepts callers, devices, or sessions too readily. Once that assumption is wrong, telemetry, fleet access, charging, and even vehicle controls can be reached through seemingly peripheral systems. Practitioners should treat authentication strength and session binding as operational safety controls, not just IT hygiene.

AI-related automotive risk is best understood as privilege misuse plus workflow trust failure. The report links malicious use of AI to manufacturing systems and enterprise agents, which shows the problem is not model capability alone but the permissions and integrations surrounding it. This is where NHI and agentic AI governance intersect: an agent, script, or automated workflow can become the attack surface when it inherits too much authority. Practitioners should govern agent permissions with the same discipline they apply to service accounts.

Command injection, missing authentication, and memory-safety flaws remain dangerous because they cross domains. In automotive settings, one weakness can move from backend services into in-vehicle systems or charging infrastructure. That creates a blast-radius problem that standard application teams often miss. The named concept here is mobility trust propagation: a local flaw becomes a broader operational issue once connected systems inherit the same trust assumptions. Practitioners should assess which controls actually contain that propagation.

Third-party exposure is now part of the core automotive attack surface. Dealer platforms, suppliers, logistics partners, and update vendors all appear in the quarter's incident pattern. This means security posture must be evaluated at the ecosystem level, not only within the OEM perimeter. Practitioners should require offboarding, access review, and integrity checks across the supplier and service-provider chain.

What this signals

Mobility trust propagation: automotive risk now moves through APIs, update paths, supplier connections, and AI workflows, so security teams need to govern the connections between systems as carefully as the systems themselves. This is where identity, access scope, and software integrity become operational controls rather than compliance artefacts.

The practical shift is toward ecosystem control mapping. Teams should know which services can reach fleet data, charging actions, vehicle functions, or enterprise agents, and they should verify that each path is authenticated, scoped, and revocable before a compromise turns into operational disruption.

For practitioners

• Audit external trust boundaries in fleet and charging services Inventory every externally reachable API, relayable authentication flow, and device-to-cloud handshake that can reach fleet, charging, or telemetry data.
• Separate vehicle, enterprise, and supplier access paths Ensure third-party support, dealer workflows, and internal admin access do not share the same credentials, sessions, or network trust.
• Treat update chains as privileged delivery channels Verify that software and firmware update mechanisms are signed, integrity-checked, and protected from unauthorized distribution or tampering.
• Restrict AI agent permissions in operational workflows Limit browser-based and enterprise AI agents to the minimum actions they need, and review connected services such as mail and file access.
• Track ransomware exposure across the mobility value chain Include dealers, retailers, suppliers, logistics providers, and OEM support functions in ransomware scenario testing and resilience planning.

Key takeaways

• Automotive cyber risk is increasingly distributed across connected services, suppliers, charging systems, and vehicle software rather than confined to the vehicle alone.
• The report's incidents show that weak authentication, command injection, memory-safety flaws, and insecure update paths can all lead to operational impact.
• Security teams need controls that follow trust relationships across the mobility ecosystem, especially where APIs, automation, and third-party access connect systems.

Key terms

• Connected Automotive Ecosystem: The connected automotive ecosystem is the full environment of vehicles, charging infrastructure, cloud services, mobile apps, suppliers, and remote management systems that support modern mobility. Security risk spans all of these components because compromise in one area can affect availability, safety, data integrity, and trust across the wider transportation stack.
• Trust Propagation: Trust propagation is the transfer of authority, context, or assumptions from one agent or system step to the next. In multi agent environments, it can turn a single compromised input or credential into a wider incident because downstream actions inherit prior trust decisions.
• Machine Identity: The digital identity of a machine, device, or workload, such as a server, container, or VM, used to authenticate it within a network. Sometimes used interchangeably with NHI, though NHI is the broader category.
• Agentic Privilege Scope: Agentic privilege scope is the set of actions, data sources, and tools an AI agent is allowed to use at runtime. For autonomous or semi-autonomous systems, the scope must be narrow enough that a manipulated prompt cannot turn a minor task into a broad operational breach.

Deepen your knowledge

NHI Foundation Level course, the industry's only accredited NHI security programme, covers NHI governance, workload identity, and secrets management for practitioners who need to govern delegated access across complex environments. It is a fit for security teams translating identity controls into operational resilience.