# CVE-2026-19774: BlueZ A2DP Stack-based Buffer Overflow Remote Code Execution Vulnerability

> Network-adjacent attackers can execute arbitrary code with root privileges via a stack-based buffer overflow in BlueZ A2DP handling after pairing.

- **Severity:** High 7.1 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Sep 2026
- **Updated:** 16 Sep 2026
- **Also known as:** AZL-103122, DEBIAN-CVE-2026-19774, GHSA-53cx-rp5p-x795, ROOT-OS-DEBIAN-12-CVE-2026-19774, ROOT-OS-DEBIAN-13-CVE-2026-19774, UBUNTU-CVE-2026-19774, USN-8908-2

## What is CVE-2026-19774?

CVE-2026-19774 is a high-severity memory corruption vulnerability in BlueZ, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

BlueZ A2DP Stack-based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of BlueZ. An attacker must first obtain the ability to pair a malicious Bluetooth device with the target system in order to exploit this vulnerability.

The specific flaw exists within the handling of the stream endpoints. 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-29429.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2026-19774?


## How do I fix CVE-2026-19774?

Apply the vendor's patch.

## Is CVE-2026-19774 being exploited?

There is no known exploitation of CVE-2026-19774 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-19774 and fix it if it is affected.

What it is: CVE-2026-19774 is a high-severity memory corruption vulnerability in BlueZ, published on 15 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-19774 in the wild and no public exploit code.

Affected product: BlueZ. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-19774/ (Markdown: https://insights.sbomify.com/CVE-2026-19774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-19774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-19774
- OSV: https://osv.dev/vulnerability/CVE-2026-19774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-19774/
Summaries are generated and may contain mistakes; the official description above is the record.