| CVE-2024-54560 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
Mar 10, 2025 |
| CVE-2024-44192 |
The issue was addressed with improved checks
|
6.5
Medium
|
Mar 10, 2025 |
| CVE-2024-54658 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Feb 10, 2025 |
| CVE-2024-27859 |
The issue was addressed with improved memory handling
|
8.8
High
|
Feb 10, 2025 |
| CVE-2025-24126 |
An input validation issue was addressed
|
9.8
Critical
|
Jan 27, 2025 |
| CVE-2024-54523 |
The issue was addressed with improved bounds checks
|
9.1
Critical
|
Jan 27, 2025 |
| CVE-2025-24107 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Jan 27, 2025 |
| CVE-2024-54543 |
The issue was addressed with improved memory handling
|
8.8
High
|
Jan 27, 2025 |
| CVE-2024-54522 |
The issue was addressed with improved bounds checks
|
7.8
High
|
Jan 27, 2025 |
| CVE-2025-24127 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54518 |
The issue was addressed with improved bounds checks
|
5.3
Medium
|
Jan 27, 2025 |
| CVE-2025-24131 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24086 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24161 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54499 |
A use-after-free issue was addressed with improved memory management
|
8.1
High
|
Jan 27, 2025 |
| CVE-2025-24137 |
A type confusion issue was addressed with improved checks
|
8.0
High
|
Jan 27, 2025 |
| CVE-2025-24160 |
The issue was addressed with improved checks
|
4.3
Medium
|
Jan 27, 2025 |
| CVE-2024-54497 |
The issue was addressed with improved checks
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54478 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24159 |
A validation issue was addressed with improved logic
|
7.8
High
|
Jan 27, 2025 |
| CVE-2025-24163 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24162 |
This issue was addressed through improved state management
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24123 |
The issue was addressed with improved checks
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24158 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24085 |
Exploited
Apple Multiple Products Use-After-Free Vulnerability
|
10.0
Critical
|
Jan 27, 2025 |