# CVE-2026-80185: Bluez: sdp-xml: bluez 5.86: unprivileged-local and adjacent-le-peer leads to arbitrary code execution as root

> A type confusion in BlueZ SDP XML parser allows local attackers or adjacent peers to execute arbitrary code as root or crash the Bluetooth daemon.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-80185, DEBIAN-CVE-2026-80185, GHSA-822r-m33h-gr5v, UBUNTU-CVE-2026-80185

## What is CVE-2026-80185?

CVE-2026-80185 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

BlueZ sdp-xml.c type confusion via RegisterProfile(ServiceRecord) can crash bluetoothd (local DoS): a crafted nested ServiceRecord can corrupt the SDP XML parser stack so scalar union data is treated as a sequence pointer, allowing a local caller to crash bluetoothd.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

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


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

Apply the vendor's patch.

## Is CVE-2026-80185 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80185 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 25 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-80185 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-80185/ (Markdown: https://insights.sbomify.com/CVE-2026-80185/index.md)
```

## Sources

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

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