dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-32059

HIGH · 8.8 CVSS v3.1 Published 2026-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The specific flaw exists within the Bluetooth stack developed by Alps Alpine of the Infotainment ECU manufactured by Bosch. The issue results from the lack of proper boundary validation of user-supplied data, which can result in a stack-based buffer overflow when receiving a specific packet on the established upper layer L2CAP channel. An attacker can leverage this vulnerability to obtain remote code execution on the Infotainment ECU with root privileges. First identified on Nissan Leaf ZE1 manufactured in 2020.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow vulnerability exists in the Alps Alpine Bluetooth stack within Bosch-manufactured Infotainment ECUs. The flaw stems from insufficient boundary validation of user-supplied data received on an established L2CAP channel, allowing an attacker to trigger the overflow via specially crafted packets and achieve remote code execution with root privileges. This issue was first identified in the Nissan Leaf ZE1 (2020 model year).

MitigationApply the vendor-supplied firmware patch to the Infotainment ECU and consider network segmentation or Bluetooth disabling as temporary risk reduction measures if the update cannot be deployed immediately.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Infotainment ECU model
    Locate the Bosch Infotainment ECU model number via system information, hardware labels, or vehicle diagnostic interface. Common identifiers include head unit part numbers or firmware banners during boot.
    Affected if The system is a Bosch infotainment unit and the Bluetooth stack is from Alps Alpine.
  2. Confirm Alps Alpine Bluetooth stack presence
    Examine Bluetooth module firmware, driver, or daemon information. On Linux-based head units, check 'hciconfig -a' output, Bluetooth stack logs, or firmware files in /lib/firmware/ and /etc/bluetooth/ for 'Alps' or 'alps' references.
    Affected if The Bluetooth implementation uses Alps Alpine firmware or drivers.
  3. Verify Bluetooth is enabled
    Check if the Bluetooth adapter is powered on via 'hciconfig' or equivalent diagnostic tool. If Bluetooth is disabled, the L2CAP processing path is not active.
    Affected if Bluetooth is powered on and the L2CAP stack is running, exposing the vulnerability.
  4. Inspect L2CAP configuration
    Review Bluetooth configuration files or runtime L2CAP settings. Use 'btmon' or 'hcidump' to observe if L2CAP channels can be established. Check for any L2CAP-specific filter or access control rules.
    Affected if L2CAP channel handling is permitted and accessible to attackers.
  5. Check for signs of compromise
    Monitor for unexpected processes, unusual network connections, or unauthorized code execution. Review system logs for anomalous Bluetooth pairing events or L2CAP connection errors. Look for new binaries or modified firmware in the infotainment system.
    Affected if There is evidence of remote code execution, new root-level processes, or modified firmware that did not originate from official updates.

A user is affected if their system is a Bosch Infotainment ECU running an Alps Alpine Bluetooth stack with Bluetooth enabled and L2CAP channel processing active.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware patch to the Infotainment ECU and consider network segmentation or Bluetooth disabling as temporary risk reduction measures if the update cannot be deployed immediately.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation32.0 h
  • Testing24.0 h
  • Review / QA12.0 h
80.0 hours of engineering $13,920
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32059 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32059 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data