Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker stages malicious Bluetooth device in range
-
DeliveryVictim connects head unit to device
-
ExploitSend crafted vCard with oversized field
-
ExecutionOverflow fixed-length stack buffer in parser
-
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 the attacker to be within Bluetooth (adjacent-network, AV:A) range and requires active user interaction: the victim must initiate a connection from the iLX-F511 to the attacker's malicious Bluetooth device, after which a crafted vCard is parsed. No authentication is needed (PR:N). The vulnerable code path is vCard parsing - i.e., contact/address-book data exchanged over the Bluetooth connection. Limiting factors that reduce real-world risk: the attacker cannot reach the device over the internet or standard IP networks (proximity-bound), and no exploitation occurs unless the user actively connects to the malicious device; the affected build is iLX-F511 7.0.0000. No non-default configuration is called out as a prerequisite in the available sources. |
| Impact | This is a genuinely serious flaw but with naturally constrained reach, so it is a priority to patch rather than a widespread-exploitation emergency. The CVSS 3.0 vector (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.0 High) confirms unauthenticated (PR:N), low-complexity exploitation yielding full confidentiality, integrity and availability loss - consistent with the description's claim of arbitrary code execution as root. The limiting signals are the adjacent-network vector (AV:A, Bluetooth range only) and required user interaction (UI:R, the victim must connect to the attacker's malicious Bluetooth device), which prevent remote, hands-off mass exploitation. No EPSS score, no CISA KEV listing, and no verified exploit code are present in the input; the sole reference is the ZDI advisory itself. The vuln.today priority is 'this_week' (not act_now/emergency), aligning with a high-impact but interaction-gated, proximity-limited issue. In short: a real, root-level RCE worth prompt remediation, but not evidence of active or automatable widespread exploitation. |
| Exploit ScenarioDerived | An attacker within Bluetooth range sets up a malicious device and induces the victim to pair/connect their Alpine iLX-F511 head unit to it; the device then sends a crafted vCard whose over-long field overflows a fixed-length stack buffer during parsing, giving the attacker code execution as root on the unit. No public, verified exploit code is identified in the input - only the ZDI advisory reference. The adjacent-only vector and required user connection keep this to targeted, close-proximity attacks rather than remote mass exploitation. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
A stack-based buffer overflow in the vCard parser of the Alpine iLX-F511 in-dash multimedia receiver (build 7.0.0000) lets an attacker within Bluetooth range execute arbitrary code as root on the head unit. The attacker must operate a malicious Bluetooth device and convince the user to connect the iLX-F511 to it, after which a crafted vCard containing contact data is parsed without adequate length validation and overruns a fixed-length stack buffer; no authentication is required on the attacker's side. Reach is proximity-bound and dependent on that deliberate user-initiated pairing, and no public exploit code was identified at time of analysis, so this is a patch-priority issue rather than a mass-exploitation emergency. The flaw was reported through the Zero Day Initiative as ZDI-CAN-29017 / ZDI-26-821.
RemediationAI
No vendor-released patch identified at time of analysis: the available intelligence contains no fixed firmware version for the Alpine iLX-F511, and the only reference is the ZDI advisory ZDI-26-821 (https://www.zerodayinitiative.com/advisories/ZDI-26-821/), which should be monitored for a vendor fix or coordinated disclosure update. Until a fixed build is published, the effective controls are at the Bluetooth layer, since the vulnerable code path is only reached after a connection to an attacker-controlled device is established. Disable Bluetooth on the head unit, or at minimum turn off discoverability and refuse pairing with unknown or untrusted devices - the trade-off is loss of hands-free calling and audio streaming. Avoid initiating connections to unrecognized Bluetooth devices and decline any contact or address-book (vCard) synchronization request from a device that is not personally controlled, which removes the user-interaction step the exploit depends on at the cost of convenience for legitimate contact syncing. Because the attack is proximity-bound, keeping the vehicle's interior/Bluetooth environment free of unattended pairing attempts by unknown parties during service visits or in public parking areas also reduces exposure. Re-check the ZDI advisory and Alpine firmware release notes before concluding that no fix exists.
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 CWE-121 stack-based buffer overflow in the firmware's vCard (contact/address-book) parsing path. vCard is a plain-text interchange format used to move contact entries between devices, and on this head unit such records are received over a Bluetooth connection, meaning the attacker's input arrives through a proximity-limited wireless channel rather than IP networking. The parser copies attacker-supplied field data into a fixed-length stack buffer without validating its length first, so an oversized value overwrites adjacent stack memory and, per the vendor report, can be shaped into code execution in the context of root - the highest privilege level on the device. The supplied CVSS vector (AV:A/AC:L/PR:N/UI:R) confirms the attack surface is adjacent-network Bluetooth with no attacker credentials, but the target user must actively initiate the connection to the malicious device; the triggering fields and exact overflow offset are not described in the available sources. The CPE cpe:2.3:a:alpine:ilx-f511:*:*:*:*:*:*:*:* is unversioned, while ENISA EUVD (EUVD-2026-112196) pins the affected build to iLX-F511 7.0.0000, and no non-default configuration is identified as a prerequisite.
Know when Bluetooth 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:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Bluetooth proximity gives AV:A; no auth is PR:N; victim must connect to the malicious device so UI:R; root-level code execution yields C:H/I:H/A:H with no scope change (S:U).
Primary rating from Vendor (zdi).
CVSS VectorVendor: zdi
DescriptionCVE.org
Alpine iLX-F511 vCard Parsing Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected Alpine iLX-F511 devices. User interaction is required to exploit this vulnerability in that the target must connect to a malicious Bluetooth device.
The specific flaw exists within the parsing of vCard data. The issue results from the lack of proper validation 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-29017.
Zero Day Initiative Advisories
Executive ViewAI
Alpine iLX-F511 in-dash multimedia receivers (build 7.0.0000) contain a high-severity stack buffer overflow in the vCard parser that can be exploited by an attacker within Bluetooth range, requiring the user to connect to a malicious Bluetooth device. Successful exploitation allows arbitrary code execution as root on the head unit, potentially compromising vehicle safety and data. Leadership should prioritize patching because this affects a safety-critical automotive component, though exploitation requires proximity and user-initiated pairing, limiting mass exploitation risk.
No vendor-released patch identified at time of analysis; interim mitigations include disabling Bluetooth pairing or limiting it to pre-approved devices, user awareness training to avoid connecting to unknown devices, and physical security of vehicles to reduce proximity attacks.
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.
Unauthenticated Bluetooth Low Energy OTA firmware upgrade in the Meatmeet Pro WiFi & Bluetooth Meat Thermometer firmware
CVE-2025-32879 is a security vulnerability (CVSS 8.8) that allows an attacker. Risk factors: public PoC available.
Zephyr's Bluetooth Low Energy connection-response handler fails to verify that a connection request was actually initiat
Heap OOB write in Android Bluetooth driver via incorrect bounds check.
A use-after-free in the Android Bluetooth stack (bluetooth_ccc.cc, function BluetoothCccHandlerCallbackImpl) lets an att
Legacy pairing and secure-connections pairing authentication in Bluetooth BR/EDR Core Specification v5.2 and earlier may
Memory corruption in the Zephyr RTOS LE Audio Broadcast Sink (subsys/bluetooth/audio/bap_broadcast_sink.c) lets an attac
A memory leak combined with a use-after-free in the Linux kernel's Bluetooth HCI connection-setup path can crash the ker
A race condition in the Linux kernel's Bluetooth L2CAP subsystem allows a use-after-free of the hci_conn::l2cap_data poi
Bluetooth authentication bypass in SwitchBot Door Lock Series allows an attacker within BLE range to manipulate the lock
Out-of-bounds read in the Linux kernel Bluetooth subsystem's eir_get_service_data() leaks kernel heap memory into usersp
Use-after-free in the Linux kernel Bluetooth L2CAP stack lets a Bluetooth-adjacent attacker corrupt kernel memory by rac
EUVD-2026-112196
GHSA-557m-98q5-chvg
NVD
CVE.org
Exploit-DB