ADVISORY | IMPACT | CVE | LAST UPDATED | VERSION |
Critical | CVE-2024-29847 | 18/09/2024 | 1.0 | |
Critical | -- | 26/09/2024 | 1.0 | |
Critical | CVE-2024-45519 | 03/10/2024 | 1.0 | |
Critical | -- | 10/10/2024 | 1.0 | |
Critical | CVE-2024-23113 | 16/10/2024 | 1.0 | |
Critical | CVE-2024-40711 | 17/10/2024 | 1.0 | |
Critical | -- | 22/10/2024 | 1.0 | |
Critical | CVE-2024-38812, CVE-2024-38813 | 23/10/2024 | 1.0 | |
Critical | CVE-2024-5910 | 08/11/2024 | 1.0 | |
High | -- | 13/11/2024 | 1.0 | |
High | CVE-2024-49040 | 27/11/2024 | 1.0 | |
Medium | CVE-2024-0139 | 29/11/2024 | 1.0 | |
Critical | CVE-2024-42448, CVE-2024-42449 | 05/12/2024 | 1.0 | |
High | -- | 10/12/2024 | 1.0 | |
High | -- | 12/12/2024 | 1.0 | |
Critical | Not yet assigned | 13/12/2024 | 1.0 | |
Critical | CVE-2024-11972 | 17/12/2024 | 1.0 | |
Critical | CVE-2024-55956, CVE-2024-50623 | 18/12/2024 | 1.0 | |
Critical | CVE-2024-50379, CVE-2024-54677 | 21/12/2024 | 1.0 | |
High | CVE-2024-3393 | 03/01/2025 | 1.0 | |
Critical | CVE-2024-49113 | 06/01/2025 | 1.1 | |
High | CVE-2024-43641 | 07/01/2025 | 1.0 | |
High | CVE-2024-6387 | 09/01/2025 | 1.0 | |
High | CVE-2025-0282, CVE-2025-0283 | 10/01/2025 | 1.0 | |
High | -- | 13/01/2025 | 1.0 | |
High | CVE-2024-53704 | 15/01/2025 | 1.0 | |
High | -- | 15/01/2025 | 1.0 | |
Critical | -- | 16/01/2025 | 1.0 | |
Critical | CVE-2024-9636 | 17/01/2025 | 1.0 | |
High | CVE-2024-49138 | 20/01/2025 | 1.0 | |
Critical | CVE-2024-55591 | 23/01/2025 | 1.0 | |
Critical | CVE-2025-20156 | 24/01/2025 | 1.0 | |
High | CVE-2024-56626, CVE-2024-56627 | 29/01/2025 | 1.0 | |
High | CVE-2025-24085 | 29/01/2025 | 1.0 | |
Critical | CVE-2025-24118 | 03/02/2025 | 1.0 | |
High | -- | 05/02/2025 | 1.0 | |
Critical | CVE-2024-21413 | 07/02/2025 | 1.0 | |
High | CVE-2025-0411 | 10/02/2025 | 1.0 | |
High | -- | 12/02/2025 | 1.0 | |
High | -- | 12/02/2025 | 1.0 | |
Critical | CVE-2025-24472 | 13/02/2025 | 1.0 | |
High | CVE-2025-0108 | 20/02/2025 | 1.0 | |
High | CVE-2025-20029 | 24/02/2025 | 1.0 | |
Critical | CVE-2025-1128 | 27/02/2025 | 1.0 | |
High | CVE-2025-20111 | 28/02/2025 | 1.0 | |
Critical | CVE-2025-24016 | 04/03/2025 | 1.0 | |
High | CVE-2018-8639 | 05/03/2025 | 1.0 | |
Critical | CVE-2025-0159, CVE-2025-0160 | 06/03/2025 | 1.0 | |
Critical | CVE-2025-22224, CVE-2025-22225, CVE-2025-22226 | 07/03/2025 | 1.0 | |
Critical | CVE-2025-25012 | 07/03/2025 | 1.0 | |
High | CVE-2024-53104 | 11/03/2025 | 1.0 | |
High | CVE-2025-24043 | 12/03/2025 | 1.0 | |
Critical | -- | 13/03/2025 | 1.0 | |
High | CVE-2025-27440, CVE-2025-27439, CVE-2025-0151, CVE-2025-0150, CVE-2025-0149 | 14/03/2025 | 1.0 | |
Medium | CVE-2025-27017 | 17/03/2025 | 1.0 | |
Critical | CVE-2025-24813 | 20/03/2025 | 1.0 | |
Critical | CVE-2025-2505 | 24/03/2025 | 1.0 | |
High | CVE-2025-2476 | 25/03/2025 | 1.0 | |
Critical | N/A | 25/03/2025 | 1.0 | |
Critical | Zero-Day | 28/03/2025 | 1.0 | |
High | CVE-2025-2783 | 28/03/2025 | 1.0 | |
High | CVE-2025-24201, CVE-2025-24085, and CVE-2025-24200. | 02/04/2025 | 1.0 | |
High | CVE-2025-2008, CVE- 2025-2007 | 03/04/2025 | 1.0 | |
Medium | CVE-2025-30401 | 09/04/2025 | 1.0 | |
High | N/A | 09/04/2025 | 1.0 | |
Critical | CVE-2024-48887 | 10/04/2025 | 1.0 | |
Critical | CVE-2025-27690, CVE-2025- 26330, CVE-2025-22471 | 13/04/2025 | 1.0 | |
Critical | CVE-2025-24859 | 15/04/2025 | 1.0 | |
High | CVE-2025-24994, CVE-2025-24076 | 21/04/2025 | 1.0 | |
High | CVE-2025-21204 | 23/04/2025 | 1.0 | |
Critical | CVE-2025-31324 | 29/04/2025 | 1.0 | |
High | CVE-2025-21756 | 30/04/2025 | 1.0 | |
High | CVE-2025-2082 | 02/05/2025 | 1.0 |