This page was not yet optimized for use on mobile devices.
Qualcomm QCS9100 Firmware
Configuration details
| CPE title | Qualcomm QCS9100 Firmware |
|---|---|
| URI | cpe:2.3:o:qualcomm:qcs9100_firmware:-:*:*:*:*:*:*:* |
Linked CVEs
75 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2024-33044 | HIGH | 7.8 | 02.12.2024 | |
| CVE-2024-33056 | HIGH | 7.8 | 02.12.2024 | |
| CVE-2024-33058 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2024-38405 | MEDIUM | 6.5 | 04.11.2024 | |
| CVE-2024-38408 | CRITICAL | 9.1 | 04.11.2024 | |
| CVE-2024-38415 | HIGH | 7.8 | 04.11.2024 | |
| CVE-2024-38420 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-43046 | MEDIUM | 5.5 | 07.04.2025 | |
| CVE-2024-43051 | MEDIUM | 5.5 | 03.03.2025 | |
| CVE-2024-43056 | MEDIUM | 6.5 | 03.03.2025 | |
| CVE-2024-43065 | HIGH | 7.1 | 07.04.2025 | |
| CVE-2024-45549 | HIGH | 7.7 | 07.04.2025 | |
| CVE-2024-45551 | MEDIUM | 6.2 | 07.04.2025 | |
| CVE-2024-45558 | HIGH | 7.5 | 06.01.2025 | |
| CVE-2024-45569 | CRITICAL | 9.8 | 03.02.2025 | |
| CVE-2024-45571 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49834 | HIGH | 7.8 | 03.02.2025 | |
| CVE-2024-49835 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49838 | HIGH | 7.5 | 03.02.2025 | |
| CVE-2024-49839 | CRITICAL | 9.8 | 03.02.2025 | |
| CVE-2024-49841 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49842 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49844 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-49845 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2024-53009 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2024-53010 | HIGH | 7.8 | 03.06.2025 | |
| CVE-2024-53020 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53021 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53024 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2024-53026 | HIGH | 8.2 | 03.06.2025 | |
| CVE-2024-53027 | HIGH | 7.5 | 03.03.2025 | |
| CVE-2024-53030 | HIGH | 7.8 | 03.03.2025 | |
| CVE-2025-21422 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21427 | HIGH | 8.2 | 08.07.2025 | |
| CVE-2025-21430 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21432 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-21433 | MEDIUM | 5.5 | 08.07.2025 | |
| CVE-2025-21434 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21446 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-21448 | HIGH | 7.5 | 07.04.2025 | |
| CVE-2025-21453 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2025-21459 | HIGH | 7.5 | 06.05.2025 | |
| CVE-2025-21463 | HIGH | 7.5 | 03.06.2025 | |
| CVE-2025-21464 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21465 | MEDIUM | 6.5 | 06.08.2025 | |
| CVE-2025-21468 | HIGH | 7.8 | 06.05.2025 | |
| CVE-2025-21476 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-21481 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-21483 | CRITICAL | 9.8 | 24.09.2025 | |
| CVE-2025-21487 | HIGH | 8.2 | 24.09.2025 | |
| CVE-2025-27032 | HIGH | 7.8 | 24.09.2025 | |
| CVE-2025-27033 | MEDIUM | 6.1 | 24.09.2025 | |
| CVE-2025-27042 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27043 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27052 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27053 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27054 | HIGH | 7.8 | 09.10.2025 | |
| CVE-2025-27057 | HIGH | 7.5 | 08.07.2025 | |
| CVE-2025-27061 | HIGH | 7.8 | 08.07.2025 | |
| CVE-2025-27066 | HIGH | 7.5 | 06.08.2025 | |
| CVE-2025-27070 | HIGH | 7.8 | 04.11.2025 | |
| CVE-2025-47330 | MEDIUM | 5.5 | 07.01.2026 | |
| CVE-2025-47331 | MEDIUM | 6.1 | 07.01.2026 | |
| CVE-2025-47334 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47335 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47337 | MEDIUM | 6.7 | 07.01.2026 | |
| CVE-2025-47339 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47344 | MEDIUM | 6.4 | 07.01.2026 | |
| CVE-2025-47345 | HIGH | 8.4 | 07.01.2026 | |
| CVE-2025-47346 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47348 | HIGH | 7.8 | 07.01.2026 | |
| CVE-2025-47357 | HIGH | 7.8 | 04.11.2025 | |
| CVE-2025-47366 | HIGH | 7.8 | 02.02.2026 | |
| CVE-2025-47369 | MEDIUM | 5.5 | 07.01.2026 | |
| CVE-2025-47370 | MEDIUM | 6.5 | 04.11.2025 |
Showing 5 out of 75.
Matched certificates
This CPE has no matched certificates.