# CVE-2026-75032: Bluez: bluez: out-of-bounds read in avrcp parse_media_element and parse_media_folder

> A malicious Bluetooth device can cause a denial of service or expose heap memory in BlueZ via out-of-bounds reads during pairing.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:L/I:N/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:** 18 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** AZL-96861, DEBIAN-CVE-2026-75032, GHSA-7wfr-vqp9-gqc3, OESA-2026-3528, UBUNTU-CVE-2026-75032

## What is CVE-2026-75032?

CVE-2026-75032 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 18 Aug 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

A flaw was found in BlueZ. Insufficient validation of packet length fields in GetFolderItems responses within the Audio/Video Remote Control Profile (AVRCP) implementation allows a malicious Bluetooth device within range to cause an out-of-bounds memory read. This vulnerability, affecting the parse_media_element() and parse_media_folder() functions, can lead to a crash of the bluetoothd daemon, resulting in a Denial of Service (DoS). It could also potentially expose sensitive heap memory contents. Exploitation requires user interaction to pair with the malicious device.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-75032 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75032 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 18 Aug 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-75032 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-75032/ (Markdown: https://insights.sbomify.com/CVE-2026-75032/index.md)
```

## Sources

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

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