| 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-2025-24117 |
This issue was addressed with improved redaction of sensitive information
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54512 |
The issue was addressed by removing the relevant flags
|
9.1
Critical
|
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-2024-54530 |
The issue was addressed with improved checks
|
9.1
Critical
|
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 |
| CVE-2025-24149 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24124 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2024-54468 |
The issue was addressed with improved checks
|
8.2
High
|
Jan 27, 2025 |
| CVE-2024-54517 |
The issue was addressed with improved bounds checks
|
7.8
High
|
Jan 27, 2025 |
| CVE-2025-24129 |
A type confusion issue was addressed with improved checks
|
7.5
High
|
Jan 27, 2025 |
| CVE-2024-54541 |
This issue was addressed through improved state management
|
5.5
Medium
|
Jan 27, 2025 |
| CVE-2025-24113 |
The issue was addressed with improved UI
|
4.3
Medium
|
Jan 27, 2025 |
| CVE-2024-54535 |
A path handling issue was addressed with improved logic
|
4.0
Medium
|
Jan 15, 2025 |
| CVE-2024-40771 |
The issue was addressed with improved memory handling
|
8.4
High
|
Jan 15, 2025 |
| CVE-2024-27856 |
The issue was addressed with improved checks
|
7.8
High
|
Jan 15, 2025 |