This page was not yet optimized for use on mobile devices.
Qualcomm APQ8076 Firmware
Configuration details
| CPE title | Qualcomm APQ8076 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:apq8076_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
73 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2018-11816 | HIGH | 7.8 | 26.11.2024 | |
| CVE-2019-10483 | MEDIUM | 5.5 | 16.04.2020 | |
| CVE-2019-10574 | HIGH | 7.1 | 16.04.2020 | |
| CVE-2019-10588 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10593 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10594 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-10609 | CRITICAL | 9.8 | 16.04.2020 | |
| CVE-2019-10610 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14019 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14020 | CRITICAL | 9.1 | 16.04.2020 | |
| CVE-2019-14062 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14073 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2019-14074 | HIGH | 7.8 | 08.09.2020 | |
| CVE-2019-14095 | CRITICAL | 9.8 | 05.03.2020 | |
| CVE-2019-14115 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-11119 | HIGH | 7.5 | 21.01.2021 | |
| CVE-2020-11157 | HIGH | 7.5 | 02.11.2020 | |
| CVE-2020-11159 | CRITICAL | 9.1 | 09.06.2021 | |
| CVE-2020-11170 | CRITICAL | 9.8 | 22.02.2021 | |
| CVE-2020-11207 | HIGH | 7.8 | 12.11.2020 | |
| CVE-2020-11233 | HIGH | 7.0 | 09.06.2021 | |
| CVE-2020-11235 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11239 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11267 | HIGH | 7.8 | 09.06.2021 | |
| CVE-2020-11269 | HIGH | 8.8 | 22.02.2021 | |
| CVE-2020-11272 | CRITICAL | 9.8 | 22.02.2021 | |
| CVE-2020-11276 | CRITICAL | 9.1 | 22.02.2021 | |
| CVE-2020-11296 | HIGH | 7.5 | 22.02.2021 | |
| CVE-2020-11303 | MEDIUM | 5.0 | 20.10.2021 | |
| CVE-2020-3614 | CRITICAL | 9.8 | 22.06.2020 | |
| CVE-2020-3643 | MEDIUM | 5.5 | 08.09.2020 | |
| CVE-2020-3703 | CRITICAL | 9.8 | 02.11.2020 | |
| CVE-2021-1904 | MEDIUM | 5.5 | 08.09.2021 | |
| CVE-2021-1909 | HIGH | 7.8 | 09.09.2021 | |
| CVE-2021-1924 | MEDIUM | 5.5 | 12.11.2021 | |
| CVE-2021-1972 | CRITICAL | 9.8 | 08.09.2021 | |
| CVE-2021-30260 | HIGH | 7.8 | 17.09.2021 | |
| CVE-2022-22075 | MEDIUM | 5.5 | 10.03.2023 | |
| CVE-2022-22088 | HIGH | 8.8 | 09.01.2023 | |
| CVE-2022-25655 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25664 | MEDIUM | 5.5 | 19.10.2022 | |
| CVE-2022-25682 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25687 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25694 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25695 | HIGH | 7.8 | 13.12.2022 | |
| CVE-2022-25705 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-25718 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25719 | CRITICAL | 9.1 | 19.10.2022 | |
| CVE-2022-25720 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25724 | HIGH | 7.8 | 15.11.2022 | |
| CVE-2022-25743 | HIGH | 7.8 | 15.11.2022 | |
| CVE-2022-25748 | CRITICAL | 9.8 | 19.10.2022 | |
| CVE-2022-25749 | HIGH | 7.5 | 19.10.2022 | |
| CVE-2022-33213 | HIGH | 8.8 | 10.03.2023 | |
| CVE-2022-33233 | HIGH | 7.8 | 12.02.2023 | |
| CVE-2022-33238 | HIGH | 7.5 | 13.12.2022 | |
| CVE-2022-33285 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-33286 | MEDIUM | 6.5 | 09.01.2023 | |
| CVE-2022-40510 | CRITICAL | 9.8 | 08.08.2023 | |
| CVE-2022-40512 | HIGH | 7.5 | 12.02.2023 | |
| CVE-2022-40515 | CRITICAL | 9.8 | 10.03.2023 | |
| CVE-2022-40531 | HIGH | 7.8 | 10.03.2023 | |
| CVE-2022-40532 | HIGH | 7.8 | 13.04.2023 | |
| CVE-2023-21628 | HIGH | 7.8 | 06.06.2023 | |
| CVE-2023-21665 | HIGH | 7.8 | 02.05.2023 | |
| CVE-2023-28560 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-28565 | HIGH | 7.8 | 05.09.2023 | |
| CVE-2023-33019 | HIGH | 7.5 | 05.09.2023 | |
| CVE-2023-33020 | HIGH | 7.5 | 05.09.2023 | |
| CVE-2023-33033 | HIGH | 7.8 | 02.01.2024 | |
| CVE-2023-33059 | HIGH | 7.8 | 07.11.2023 | |
| CVE-2023-33066 | HIGH | 7.8 | 04.03.2024 | |
| CVE-2025-21454 | HIGH | 7.5 | 08.07.2025 |
Showing 5 out of 73.
Matched certificates
This CPE has no matched certificates.