| Date | ID | Source Package(s) | Type | Affected release(s) | CVE |
|---|---|---|---|---|---|
| 2023-12-20 | MGASA-2023-0353 | bluez | security | 9 | CVE-2023-45866 |
| 2022-11-08 | MGASA-2022-0411 | bluez | security | 8 | |
| 2022-07-12 | MGAA-2022-0102 | bluez | bugfix | 8 | |
| 2022-06-18 | MGASA-2022-0235 | bluez | security | 8 | |
| 2022-02-12 | MGASA-2022-0058 | bluez | security | 8 | CVE-2022-0204 |
| 2021-12-02 | MGASA-2021-0532 | bluez | security | 8 | CVE-2021-41229 , CVE-2021-43400 |
| 2021-08-06 | MGASA-2021-0395 | bluez | security | 8 | CVE-2021-3658 |
| 2021-06-23 | MGASA-2021-0281 | bluez | security | 8 , 7 | CVE-2020-26558 , CVE-2021-3588 |
| 2020-11-13 | MGASA-2020-0419 | bluez | security | 7 | CVE-2020-27153 |
| 2020-04-02 | MGASA-2020-0152 | bluez | security | 7 | CVE-2018-10910 , CVE-2020-0556 |
| 2019-05-12 | MGAA-2019-0030 | bluez | bugfix | 6 | |
| 2019-01-30 | MGASA-2019-0052 | bluez | security | 6 | CVE-2016-9800 , CVE-2016-9801 , CVE-2016-9804 |
| 2017-11-19 | MGASA-2017-0414 | bluez | security | 5 | CVE-2016-7837 |
| 2017-09-21 | MGASA-2017-0350 | bluez | security | 6 , 5 | CVE-2017-1000250 |
