| CVE-2025-31281 |
An input validation issue was addressed with improved memory handling
|
9.1
Critical
|
Jul 29, 2025 |
| CVE-2025-43223 |
A denial-of-service issue was addressed with improved input validation
|
7.5
High
|
Jul 29, 2025 |
| CVE-2025-43200 |
Exploited
Apple Multiple Products Unspecified Vulnerability
|
4.2
Medium
|
Jun 16, 2025 |
| CVE-2025-30466 |
This issue was addressed through improved state management
|
9.8
Critical
|
May 29, 2025 |
| CVE-2025-31199 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
May 29, 2025 |
| CVE-2025-24184 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
May 19, 2025 |
| CVE-2025-24189 |
The issue was addressed with improved checks
|
8.8
High
|
May 19, 2025 |
| CVE-2025-31262 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
May 19, 2025 |
| CVE-2025-24223 |
The issue was addressed with improved memory handling
|
8.0
High
|
May 12, 2025 |
| CVE-2025-31241 |
A double free issue was addressed with improved memory management
|
5.3
Medium
|
May 12, 2025 |
| CVE-2025-31257 |
This issue was addressed with improved memory handling
|
4.7
Medium
|
May 12, 2025 |
| CVE-2025-31217 |
The issue was addressed with improved input validation
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24111 |
A memory corruption issue was addressed with improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31221 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31206 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
May 12, 2025 |
| CVE-2025-31251 |
The issue was addressed with improved input sanitization
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31226 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31196 |
An out-of-bounds read was addressed with improved input validation
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31204 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 12, 2025 |
| CVE-2025-31212 |
This issue was addressed through improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31245 |
The issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31208 |
The issue was addressed with improved checks
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31233 |
The issue was addressed with improved input sanitization
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-31209 |
An out-of-bounds read was addressed with improved bounds checking
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-31205 |
The issue was addressed with improved checks
|
6.5
Medium
|
May 12, 2025 |