| 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-2023-42970 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Apr 11, 2025 |
| CVE-2023-42875 |
Processing web content may lead to arbitrary code execution
|
7.3
High
|
Apr 11, 2025 |
| CVE-2025-30427 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Mar 31, 2025 |
| CVE-2024-40864 |
The issue was addressed with improved handling of protocols
|
2.7
Low
|
Mar 31, 2025 |
| CVE-2025-24203 |
The issue was addressed with improved checks
|
5.0
Medium
|
Mar 31, 2025 |
| CVE-2025-31191 |
This issue was addressed through improved state management
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24238 |
A logic issue was addressed with improved checks
|
9.8
Critical
|
Mar 31, 2025 |
| CVE-2025-30447 |
The issue was resolved by sanitizing logging
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24214 |
A privacy issue was addressed by not logging contents of text fields
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24097 |
A permissions issue was addressed with additional restrictions
|
5.0
Medium
|
Mar 31, 2025 |
| CVE-2025-24243 |
The issue was addressed with improved memory handling
|
7.8
High
|
Mar 31, 2025 |
| CVE-2025-30426 |
This issue was addressed with additional entitlement checks
|
9.8
Critical
|
Mar 31, 2025 |
| CVE-2025-30471 |
A validation issue was addressed with improved logic
|
7.5
High
|
Mar 31, 2025 |
| CVE-2025-24182 |
An out-of-bounds read issue was addressed with improved input validation
|
5.5
Medium
|
Mar 31, 2025 |