Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.27% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-19774High confidence
BlueZ A2DP Stack-based Buffer Overflow Remote Code Execution Vulnerability
BlueZ · BlueZ
7.1HighCVSS 3.0
Patch only the product branches with a verified fix
Fix availability varies by productHigh technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Apply the linked authoritative mitigation while planning the permanent fix.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs BlueZ BlueZ and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 32 affected or under-investigation product states without a fixed product state in the same current advisory
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | bluez | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian bookwormbookworm · source | bluez | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian forkyforky · source | bluez | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.87-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Debian sidsid · source | bluez | Vendor fix publishedDebian records a fixed source-package version for this release. | 5.87-1 | Debian Security Tracker ↗Source updated 7 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | bluez | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 7 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-19774 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybluez: BlueZ: Arbitrary Code Execution via A2DP Stack-based Buffer Overflow
The vendor explicitly identifies these products as affected by this CVE.
- bluez-cups as a component of Red Hat Enterprise Linux 10
- bluez-libs as a component of Red Hat Enterprise Linux 10
- bluez-libs-devel as a component of Red Hat Enterprise Linux 10
- bluez-obexd as a component of Red Hat Enterprise Linux 10
- bluez.src as a component of Red Hat Enterprise Linux 10
- bluez as a component of Red Hat Enterprise Linux 6
- bluez-alsa as a component of Red Hat Enterprise Linux 6
- bluez-compat as a component of Red Hat Enterprise Linux 6
- bluez-cups as a component of Red Hat Enterprise Linux 6
- bluez-gstreamer as a component of Red Hat Enterprise Linux 6
- bluez-libs as a component of Red Hat Enterprise Linux 6
- bluez-libs-devel as a component of Red Hat Enterprise Linux 6
- Summary
- A flaw was found in BlueZ. This vulnerability, a stack-based buffer overflow in the Advanced Audio Distribution Profile (A2DP) stack, allows a network-adjacent attacker to execute arbitrary code. By pairing a malicious Bluetooth device with the target system, an attacker can exploit improper validation of user-supplied data length. Successful exploitation leads to arbitrary code execution with root privileges.
- Remediation
- To mitigate this vulnerability, disable the Bluetooth service if it is not required. This can be achieved by stopping and disabling the `bluetooth` service. ```bash sudo systemctl stop bluetooth sudo systemctl disable bluetooth ``` Disabling the Bluetooth service will prevent all Bluetooth functionality on the system. A system reboot may be required for the changes to take full effect.
High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 34 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
How
An attacker operating through an adjacent network may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
What
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.
Why
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
How
An attacker operating through an adjacent network may attempt exploitation without authentication after a user interaction. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- an adjacent network → Stack-based Buffer Overflow → execute code or commands in the affected security context
- Attack surface
- Adjacent
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- High: exploitation depends on specific conditions
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-121 ↗
CWE-121: Stack-based Buffer Overflow. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.0/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.0: the compact vector below is decoded into plain language.
AVAdjacentAttack vector: The attacker must be on an adjacent or logically close network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- bluez-cups as a component of Red Hat Enterprise Linux 10
- bluez-libs as a component of Red Hat Enterprise Linux 10
- bluez-libs-devel as a component of Red Hat Enterprise Linux 10
- bluez-obexd as a component of Red Hat Enterprise Linux 10
- bluez.src as a component of Red Hat Enterprise Linux 10
- bluez as a component of Red Hat Enterprise Linux 6
- bluez-alsa as a component of Red Hat Enterprise Linux 6
- bluez-compat as a component of Red Hat Enterprise Linux 6
- bluez-cups as a component of Red Hat Enterprise Linux 6
- bluez-gstreamer as a component of Red Hat Enterprise Linux 6
- bluez-libs as a component of Red Hat Enterprise Linux 6
- bluez-libs-devel as a component of Red Hat Enterprise Linux 6
- bluez.src as a component of Red Hat Enterprise Linux 6
- bluez as a component of Red Hat Enterprise Linux 7
- bluez-cups as a component of Red Hat Enterprise Linux 7
- bluez-hid2hci as a component of Red Hat Enterprise Linux 7
- bluez-libs as a component of Red Hat Enterprise Linux 7
- bluez-libs-devel as a component of Red Hat Enterprise Linux 7
- bluez.src as a component of Red Hat Enterprise Linux 7
- bluez as a component of Red Hat Enterprise Linux 8
- bluez-cups as a component of Red Hat Enterprise Linux 8
- bluez-hid2hci as a component of Red Hat Enterprise Linux 8
- bluez-libs as a component of Red Hat Enterprise Linux 8
- bluez-libs-devel as a component of Red Hat Enterprise Linux 8
- bluez-obexd as a component of Red Hat Enterprise Linux 8
- bluez.src as a component of Red Hat Enterprise Linux 8
- bluez as a component of Red Hat Enterprise Linux 9
- bluez-cups as a component of Red Hat Enterprise Linux 9
- bluez-libs as a component of Red Hat Enterprise Linux 9
- bluez-libs-devel as a component of Red Hat Enterprise Linux 9
- and 2 more
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- To mitigate this vulnerability, disable the Bluetooth service if it is not required. This can be achieved by stopping and disabling the `bluetooth` service. ```bash sudo systemctl stop bluetooth sudo systemctl disable bluetooth ``` Disabling the Bluetooth service will prevent all Bluetooth functionality on the system. A system reboot may be required for the changes to take full effect.
04
Evidence and provenance
Published 15 Sept 2026 · Last source change 16 Sept 2026, 03:57 UTC · CWE-121 · Stack-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-09-16
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-79131
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2026-79131 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2026-79131"}
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.