CVE-2026-118609: Alpine iLX-F511 Android Auto Connection Handler stack buffer overflow

CVE-2026-118609 · Severity: medium · CVSS 6.8 · Published 2026-10-28

The Alpine iLX-F511 is an in-car entertainment system that integrates Android Auto. A stack-based buffer overflow in its Android Auto connection handler allows an attacker with physical access to the device to execute code with root privileges without needing to authenticate. An attacker could gain complete control of the vehicle's infotainment system.

Technologies: Alpine iLX-F511. Vendors: Alpine.

Quick answers

Is CVE-2026-118609 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-118609 being exploited in the wild.
How severe is CVE-2026-118609?
Medium severity, with a CVSS score of 6.8, published 28 October 2026.
Which products and versions are affected?
Alpine iLX-F511.
Is there a fix for CVE-2026-118609?
No fixed version is recorded yet. Restrict physical interaction with the device to trusted users only. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-118609 attacked?
It is attacked with physical access, in a network appliance.
Am I affected by CVE-2026-118609?
Check whether you run Alpine iLX-F511. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Restrict physical interaction with the device to trusted users only.

Technical details

The vulnerability exists in the Android Auto connection handler due to insufficient length validation before copying user-supplied data into a fixed-length stack buffer. An attacker with physical access can send crafted data to trigger the overflow and execute arbitrary code in root context. No authentication is required to exploit this flaw.

Affected products

  • Alpine iLX-F511

Timeline

  • 2026-02-04: disclosed: Vulnerability reported to vendor
  • 2026-06-07: other: Vendor acknowledged receipt and requested extension
  • 2026-07-21: other: ZDI requested status update on fix
  • 2026-10-15: other: ZDI notified vendor of intention to publish as 0-day advisory
  • 2026-10-28: advisory: Coordinated public release of advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.