Quick answers
- Is CVE-2026-80185 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-80185 being exploited in the wild.
- How severe is CVE-2026-80185?
- Medium severity, with a CVSS score of 5.7, published 25 August 2026.
- Which products and versions are affected?
- BlueZ 5.86 and possibly earlier.
- Is there a fix for CVE-2026-80185?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-80185 attacked?
- It is attacked from the adjacent network or with local access.
- Am I affected by CVE-2026-80185?
- Check whether you run BlueZ at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A type confusion vulnerability (CWE-843) exists in BlueZ's sdp-xml.c file within the RegisterProfile() method handling. A crafted nested ServiceRecord can corrupt the SDP XML parser stack, causing scalar union data to be incorrectly treated as a sequence pointer. The vulnerability is triggered via a local caller or an adjacent Bluetooth network peer with low privileges and requires no user interaction. Exploitation results in a crash of the bluetoothd daemon (local DoS), and the parser's stack corruption could potentially allow memory read/write operations or code execution in certain configurations. Patches are available in updated BlueZ releases.
Affected products
- BlueZ BlueZ 5.86 and possibly earlier
Timeline
- 2026-08-25: disclosed