Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to head unit
-
DeliveryConnect malicious Android Auto device
-
ExploitSend over-length data to connection handler
-
ExecutionOverflow fixed-size stack buffer
-
ImpactExecute arbitrary code as root
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires physical presence at the Alpine iLX-F511 head unit (CVSS AV:P): the attacker must connect to the device's Android Auto connection handler - typically via a wired/USB Android Auto session - and supply over-length data that the handler copies into a fixed-length stack buffer without length validation. No authentication is required (PR:N) and no user interaction by a legitimate user is needed (UI:N), and the affected version is iLX-F511 7.0.000. The dominant limiting factor is the physical-access precondition: the attacker must have hands-on or local wired access to the unit, which prevents remote or network-based exploitation and constrains realistic abuse to scenarios where the vehicle/head unit is physically accessible to an untrusted party. |
| Impact | This is a genuinely high-severity vulnerability in mechanism (unauthenticated root code execution via a classic stack-based buffer overflow, CWE-121) but a moderate real-world priority because of the physical attack vector. The CVSS:3.0 vector AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (6.8, Medium) explicitly scopes exploitation to a physically present attacker: the C:H/I:H/A:H impact and root-context execution are severe, but AV:P caps the base score and reflects that remote mass-exploitation is not possible. No EPSS score was provided, no CISA KEV listing is present, and there is no confirmed public exploit code - only the ZDI advisory reference - so there are no signals of active or at-scale exploitation. The vuln.today decision label is 'this_month' (not act_now/emergency), consistent with a serious but non-emergency, physically-gated bug. The signals are internally consistent rather than conflicting: a high technical impact bounded by a physical-access precondition. The main caveat is that AV:P requires the attacker to physically interact with the head unit, so prioritization should weigh exposure of the device to untrusted physical/USB access rather than treating this as an internet-facing RCE. |
| Exploit ScenarioDerived | An attacker with physical access to a vehicle (e.g., valet, rental return, repair shop, or a briefly unattended car) connects a malicious device emulating an Android Auto phone to the Alpine iLX-F511 head unit. The connection handler copies attacker-controlled data of unchecked length into a fixed-size stack buffer, overflowing it and allowing arbitrary code execution as root. No public exploit code is identified at time of analysis; only the ZDI advisory documents the flaw. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Unauthenticated code execution as root on Alpine iLX-F511 in-car head units (version 7.0.000) is possible because the Android Auto connection handler copies attacker-supplied data into a fixed-length stack buffer without validating its length (CWE-121). Exploitation requires physical presence at the unit (CVSS AV:P); an attacker who can establish a wired Android Auto session with the head unit and deliver over-length data can corrupt the stack and redirect execution with root privileges, with no authentication (PR:N) and no action by the vehicle owner (UI:N). CVSS 3.1 base score is 6.8; CISA KEV does not list this issue, no public exploit code has been identified at time of analysis, and no EPSS estimate was supplied with the available intelligence.
RemediationAI
No vendor-released patch, fixed firmware version, or documented workaround appears in the available sources; the only authoritative reference is the ZDI advisory ZDI-26-827 (https://www.zerodayinitiative.com/advisories/ZDI-26-827/), so owners should contact Alpine support directly to confirm whether a firmware update addressing the Android Auto connection handler has shipped and to obtain the exact fixed version before relying on any upgrade. Because the assessment establishes a physical attack vector (AV:P) reachable through the unit's Android Auto connection - typically a wired/USB session - the practical lever described in the intelligence is limiting hands-on access to the head unit: keep the vehicle locked and the unit out of reach of untrusted parties, and treat any period where the vehicle or head unit is accessible to an untrusted person as an exposure window for this flaw. Where the vehicle owner is willing to give up Android Auto functionality, denying untrusted devices the ability to establish an Android Auto session with the unit reduces the attack surface, but this is an inference from the stated attack vector, not a vendor-published mitigation, and the sources do not confirm that such a setting exists on firmware 7.0.000 or that it fully closes the flaw; the ZDI advisory should be monitored for a vendor fix or an official mitigation statement.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The defect is a classic stack-based buffer overflow (CWE-121) inside the Android Auto connection handler of the Alpine iLX-F511 infotainment head unit. The handler accepts length-controlled data from the Android Auto session but does not verify that the incoming length fits the destination before performing a copy into a fixed-length stack buffer, so an over-length value overwrites adjacent stack memory, including saved control data. Because the vulnerable handler runs in the unit's privileged context, successful corruption yields code execution as root rather than in a sandboxed or unprivileged service. The CPE cpe:2.3:a:alpine:ilx-f511:*:*:*:*:*:*:*:* identifies the iLX-F511 product family broadly, while the EUVD record narrows the confirmed affected firmware to version 7.0.000; the sources do not confirm whether later or earlier firmware builds carry the same handler. The assessment places the attack vector at physical (AV:P), with the attacker connecting to the Android Auto connection handler, typically through a wired/USB Android Auto session, and no authentication or legitimate-user interaction required. The specific packet fields, offsets and copy site that trigger the overflow are not described in the available sources, and no proof-of-concept or exploit code was supplied.
Know when Ilx F511 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Physical connection to the head unit is required (AV:P), no authentication or user interaction (PR:N/UI:N), and root-context code execution yields full C:H/I:H/A:H.
Primary rating from Vendor (zdi).
CVSS VectorVendor: zdi
DescriptionCVE.org
Alpine iLX-F511 Android Auto Connection Handler Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows physically present attackers to execute arbitrary code on affected installations of Alpine iLX-F511 devices. Authentication is not required to exploit this vulnerability.
The specific flaw exists within the Android Auto connection handler. The issue results from the lack of proper validation of the length of user-supplied data prior to copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-29016.
Zero Day Initiative Advisories
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
A stack-based buffer overflow in the Android Auto service on Alpine iLX-F511 head units lets network-adjacent attackers
Remote code execution in the framework service of the Alpine iLX-F511 infotainment head unit allows network-adjacent att
A stack-based buffer overflow in the prh_sdp_service_search_decode function of the Alpine iLX-F511 in-vehicle head unit
A stack-based buffer overflow in the vCard parser of the Alpine iLX-F511 in-dash multimedia receiver (build 7.0.0000) le
Local privilege escalation in the Alpine iLX-F511 in-vehicle media receiver lets code already running as a low-privilege
A heap-based buffer overflow in the Bluetooth OBEX packet handling of the Alpine iLX-F511 in-car head unit (version 7.0.
Command injection in the 'diagapp' diagnostic component of the Alpine iLX-F511 in-dash infotainment head unit lets a phy
Stack-based buffer overflow in the framework service of the Alpine iLX-F511 in-vehicle head unit allows an attacker with
Hard-coded SSH credentials in Alpine iLX-F511 firmware 7.0.000 allow network-adjacent, unauthenticated attackers to log
An out-of-bounds read in the Bluetooth RFCOMM control-channel handler prh_rfcomm_cc_process_test (inside libanwbtstack.s
EUVD-2026-112204
GHSA-5mv5-mjhp-2hjw
NVD
CVE.org
Exploit-DB