| CVE-2025-43501 |
A buffer overflow issue was addressed with improved memory handling
|
4.3
Moyenne
|
17 déc. 2025 |
| CVE-2025-43538 |
A logging issue was addressed with improved data redaction
|
3.3
Faible
|
12 déc. 2025 |
| CVE-2025-43539 |
The issue was addressed with improved bounds checks
|
8.8
Élevée
|
12 déc. 2025 |
| CVE-2025-43542 |
This issue was addressed with improved state management
|
7.5
Élevée
|
12 déc. 2025 |
| CVE-2025-46287 |
An inconsistent user interface issue was addressed with improved state management
|
9.8
Critique
|
12 déc. 2025 |
| CVE-2025-43494 |
A mail header parsing issue was addressed with improved checks
|
7.5
Élevée
|
12 déc. 2025 |
| CVE-2025-43532 |
A memory corruption issue was addressed with improved bounds checking
|
2.8
Faible
|
12 déc. 2025 |
| CVE-2025-46285 |
An integer overflow was addressed by adopting 64-bit timestamps
|
7.8
Élevée
|
12 déc. 2025 |
| CVE-2025-43510 |
Exploitée
Apple Multiple Products Improper Locking Vulnerability
|
7.8
Élevée
|
12 déc. 2025 |
| CVE-2025-43511 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
12 déc. 2025 |
| CVE-2025-46276 |
An information disclosure issue was addressed with improved privacy controls
|
3.3
Faible
|
12 déc. 2025 |
| CVE-2025-43520 |
Exploitée
Apple Multiple Products Classic Buffer Overflow Vulnerability
|
5.5
Moyenne
|
12 déc. 2025 |
| CVE-2025-43374 |
An out-of-bounds read was addressed with improved bounds checking
|
4.3
Moyenne
|
21 nov. 2025 |
| CVE-2025-43205 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.0
Moyenne
|
12 nov. 2025 |
| CVE-2025-43430 |
This issue was addressed through improved state management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43447 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43502 |
A privacy issue was addressed by removing sensitive data
|
7.5
Élevée
|
4 nov. 2025 |
| CVE-2025-43386 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
Élevée
|
4 nov. 2025 |
| CVE-2025-43345 |
A correctness issue was addressed with improved checks
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43493 |
The issue was addressed with improved checks
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43503 |
An inconsistent user interface issue was addressed with improved state management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43407 |
This issue was addressed with improved entitlements
|
7.8
Élevée
|
4 nov. 2025 |
| CVE-2025-43427 |
This issue was addressed through improved state management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43431 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
4 nov. 2025 |
| CVE-2025-43379 |
This issue was addressed with improved validation of symlinks
|
5.5
Moyenne
|
4 nov. 2025 |