VulertSecurity VulertSecurity

Vulnerability Database · OSS-Fuzz · Package report

bluez: vulnerability history, versions and safety

bluez is a package in the OSS-Fuzz ecosystem. Vulert records 3 vulnerabilities for it across 18 releases, first recorded in Sep 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H1 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all bluez vulnerabilities

Vulert verdict on bluez i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 18 Sep 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 3 vulnerabilities on record across 1 year, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 3 over 1 year · 0 in the last year i
  • Latest disclosure 18 Sep 2022 i
  • Highest CVSS n/a i
  • With no published fix 0 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for bluez, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
5.83 M1 Yes Details →
5.82 M1 Yes Details →
5.81 M1 Yes Details →
5.80 M1 Yes Details →
5.79 M1 Yes Details →
5.78 M2 Yes Details →
5.77 M2 Yes Details →
5.76 M2 Yes Details →
5.75 M2 Yes Details →
5.74 M2 Yes Details →
5.73 M2 Yes Details →
5.72 M2 Yes Details →
5.71 M2 Yes Details →
5.70 M2 Yes Details →
5.69 M2 Yes Details →
5.68 M2 Yes Details →
5.67 M2 Yes Details →
5.66 M2 Yes Details →

Newest 18 of 18 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 3 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for bluez

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-double-free vulnerability in bluez package N/A high 4c8a6ba5ec7fb82e77710c69f14f774aa4c348a9 08 Sep 2022
Vulnerability in bluez: UNKNOWN READ in write_key N/A medium 0845b8f6ef2ac004b1c953cf4fe4ca3458cd8e36 08 Sep 2022
Heap-buffer-overflow in element_end in bluez N/A medium 00eea35722b73d922472c7fba006f711690ce195 18 Sep 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About bluez

Is bluez safe to use?

Vulert records 3 vulnerabilities for bluez in OSS-Fuzz: 0 critical, 1 high, 2 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

How many vulnerabilities does bluez have?

3 vulnerabilities are recorded for bluez in the OSS-Fuzz ecosystem: 0 critical, 1 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new bluez vulnerabilities disclosed?

0 vulnerabilities were recorded for bluez in the last 12 months, and the oldest entry in this database dates to 08 Sep 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of bluez are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor bluez for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the bluez version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.