| CVE-2024-44271 |
The issue was addressed with improved checks
|
3.3
Faible
|
29 août 2025 |
| CVE-2025-43268 |
A permissions issue was addressed with additional restrictions
|
7.8
Élevée
|
29 août 2025 |
| CVE-2025-43255 |
An out-of-bounds read was addressed with improved bounds checking
|
3.3
Faible
|
29 août 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-43191 |
A path handling issue was addressed with improved validation
|
6.2
Moyenne
|
29 juil. 2025 |
| CVE-2025-43237 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43197 |
This issue was addressed with additional entitlement checks
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43206 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43196 |
A path handling issue was addressed with improved validation
|
7.8
Élevée
|
29 juil. 2025 |
| CVE-2025-43265 |
An out-of-bounds read was addressed with improved input validation
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43233 |
This issue was addressed with improved access restrictions
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43218 |
An out-of-bounds read was addressed with improved input validation
|
5.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-24188 |
A logic issue was addressed with improved checks
|
6.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-43216 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-43186 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43276 |
A logic error was addressed with improved error handling
|
5.3
Moyenne
|
29 juil. 2025 |
| CVE-2025-43260 |
This issue was addressed with improved data protection
|
5.1
Moyenne
|
29 juil. 2025 |
| CVE-2025-43247 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-43230 |
The issue was addressed with additional permissions checks
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43226 |
An out-of-bounds read was addressed with improved input validation
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-24224 |
The issue was addressed with improved checks
|
7.5
Élevée
|
29 juil. 2025 |
| CVE-2025-43227 |
This issue was addressed through improved state management
|
7.5
Élevée
|
29 juil. 2025 |
| CVE-2025-43270 |
An access issue was addressed with additional sandbox restrictions
|
8.8
Élevée
|
29 juil. 2025 |
| CVE-2025-43266 |
A permissions issue was addressed with additional restrictions
|
5.1
Moyenne
|
29 juil. 2025 |
| CVE-2025-43211 |
The issue was addressed with improved memory handling
|
6.2
Moyenne
|
29 juil. 2025 |