| CVE-2025-30448 |
This issue was addressed with additional entitlement checks
|
9.1
Critical
|
May 12, 2025 |
| CVE-2025-31234 |
The issue was addressed with improved input sanitization
|
8.2
High
|
May 12, 2025 |
| CVE-2025-31222 |
A correctness issue was addressed with improved checks
|
7.8
High
|
May 12, 2025 |
| CVE-2025-31238 |
The issue was addressed with improved checks
|
7.3
High
|
May 12, 2025 |
| CVE-2025-31242 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31239 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
May 12, 2025 |
| CVE-2025-31215 |
The issue was addressed with improved checks
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24144 |
An information disclosure issue was addressed by removing the vulnerable code
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31223 |
The issue was addressed with improved checks
|
8.0
High
|
May 12, 2025 |
| CVE-2025-31219 |
The issue was addressed with improved memory handling
|
7.1
High
|
May 12, 2025 |
| CVE-2025-24252 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Apr 29, 2025 |
| CVE-2025-31197 |
The issue was addressed with improved checks
|
5.7
Medium
|
Apr 29, 2025 |
| CVE-2025-24179 |
A null pointer dereference was addressed with improved input validation
|
5.7
Medium
|
Apr 29, 2025 |
| CVE-2025-24270 |
This issue was addressed by removing the vulnerable code
|
5.7
Medium
|
Apr 29, 2025 |
| CVE-2025-24271 |
An access issue was addressed with improved access restrictions
|
5.4
Medium
|
Apr 29, 2025 |
| CVE-2025-24206 |
An authentication issue was addressed with improved state management
|
7.7
High
|
Apr 29, 2025 |
| CVE-2025-31202 |
A null pointer dereference was addressed with improved input validation
|
5.5
Medium
|
Apr 29, 2025 |
| CVE-2025-24251 |
The issue was addressed with improved checks
|
6.5
Medium
|
Apr 29, 2025 |
| CVE-2025-31203 |
An integer overflow was addressed with improved input validation
|
6.5
Medium
|
Apr 29, 2025 |
| CVE-2025-30445 |
A type confusion issue was addressed with improved checks
|
6.5
Medium
|
Apr 29, 2025 |
| CVE-2025-31201 |
Exploited
Apple Multiple Products Arbitrary Read and Write Vulnerability
|
9.8
Critical
|
Apr 16, 2025 |
| CVE-2025-31200 |
Exploited
Apple Multiple Products Memory Corruption Vulnerability
|
9.8
Critical
|
Apr 16, 2025 |
| CVE-2025-30470 |
A path handling issue was addressed with improved logic
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-30427 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Mar 31, 2025 |
| CVE-2025-24203 |
The issue was addressed with improved checks
|
5.0
Medium
|
Mar 31, 2025 |