| CVE-2025-43362 |
The issue was addressed with improved checks
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43342 |
A correctness issue was addressed with improved checks
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-31255 |
An authorization issue was addressed with improved state management
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43347 |
This issue was addressed by removing the vulnerable code
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43300 |
Exploitée
Apple iOS, iPadOS, and macOS Out-of-Bounds Write Vulnerability
|
10.0
Critique
|
21 août 2025 |
| CVE-2025-43186 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43209 |
An out-of-bounds access issue was addressed with improved bounds checking
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43234 |
Multiple memory corruption issues were addressed with improved input validation
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-31229 |
A logic issue was addressed with improved checks
|
9.1
Critique
|
29 juil. 2025 |
| CVE-2025-31281 |
An input validation issue was addressed with improved memory handling
|
9.1
Critique
|
29 juil. 2025 |
| CVE-2025-30466 |
This issue was addressed through improved state management
|
9.8
Critique
|
29 mai 2025 |
| CVE-2025-30436 |
This issue was addressed by restricting options offered on a locked device
|
9.1
Critique
|
12 mai 2025 |
| CVE-2025-30448 |
This issue was addressed with additional entitlement checks
|
9.1
Critique
|
12 mai 2025 |
| CVE-2025-31201 |
Exploitée
Apple Multiple Products Arbitrary Read and Write Vulnerability
|
9.8
Critique
|
16 avr. 2025 |
| CVE-2025-31200 |
Exploitée
Apple Multiple Products Memory Corruption Vulnerability
|
9.8
Critique
|
16 avr. 2025 |
| CVE-2025-24167 |
This issue was addressed through improved state management
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-24238 |
A logic issue was addressed with improved checks
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-30426 |
This issue was addressed with additional entitlement checks
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-30430 |
This issue was addressed through improved state management
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-24264 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-31183 |
The issue was addressed with improved restriction of data container access
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-24211 |
This issue was addressed with improved memory handling
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-24230 |
An out-of-bounds read issue was addressed with improved input validation
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-24178 |
This issue was addressed through improved state management
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-31182 |
This issue was addressed with improved handling of symlinks
|
9.8
Critique
|
31 mars 2025 |