Root code execution via undersized codec buffer
Published Sep 15, 2026 · Updated Sep 15, 2026
Stack-based buffer overflow in BlueZ A2DP allows network-adjacent attackers to execute arbitrary code as root through a paired device. The store_remote_sep path encodes up to 255 codec-capability bytes as two-character hexadecimal values without reserving enough stack storage. The malicious Bluetooth device must first be paired, after which crafted stream-endpoint data can corrupt the bluetoothd stack.
Summary
What happened
Stack-based buffer overflow in BlueZ A2DP allows network-adjacent attackers to execute arbitrary code as root through a paired device. The store_remote_sep path encodes up to 255 codec-capability bytes as two-character hexadecimal values without reserving enough stack storage. The malicious Bluetooth device must first be paired, after which crafted stream-endpoint data can corrupt the bluetoothd stack.
The record
- CVE
- CVE-2026-19774
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- BlueZ
- Product
- BlueZ
- Classifications
- CWE-121, T1203
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=b138a0849ba26310c3f40e78037565ce274d8737
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo