| CVE-2025-31205 |
The issue was addressed with improved checks
|
6.5
Moyenne
|
12 mai 2025 |
| CVE-2025-31222 |
A correctness issue was addressed with improved checks
|
7.8
Élevée
|
12 mai 2025 |
| CVE-2025-31238 |
The issue was addressed with improved checks
|
7.3
Élevée
|
12 mai 2025 |
| CVE-2025-31242 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.5
Moyenne
|
12 mai 2025 |
| CVE-2025-31239 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
12 mai 2025 |
| CVE-2025-31215 |
The issue was addressed with improved checks
|
6.5
Moyenne
|
12 mai 2025 |
| CVE-2025-24144 |
An information disclosure issue was addressed by removing the vulnerable code
|
5.5
Moyenne
|
12 mai 2025 |
| CVE-2025-31223 |
The issue was addressed with improved checks
|
8.0
Élevée
|
12 mai 2025 |
| CVE-2025-31219 |
The issue was addressed with improved memory handling
|
7.1
Élevée
|
12 mai 2025 |
| CVE-2025-24251 |
The issue was addressed with improved checks
|
6.5
Moyenne
|
29 avr. 2025 |
| CVE-2025-31203 |
An integer overflow was addressed with improved input validation
|
6.5
Moyenne
|
29 avr. 2025 |
| CVE-2025-31200 |
Exploitée
Apple Multiple Products Memory Corruption Vulnerability
|
9.8
Critique
|
16 avr. 2025 |
| CVE-2023-42970 |
A use-after-free issue was addressed with improved memory management
|
8.8
Élevée
|
11 avr. 2025 |
| CVE-2023-42875 |
Processing web content may lead to arbitrary code execution
|
7.3
Élevée
|
11 avr. 2025 |
| CVE-2025-24167 |
This issue was addressed through improved state management
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-30470 |
A path handling issue was addressed with improved logic
|
5.5
Moyenne
|
31 mars 2025 |
| CVE-2025-30427 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
31 mars 2025 |
| CVE-2024-40864 |
The issue was addressed with improved handling of protocols
|
2.7
Faible
|
31 mars 2025 |
| CVE-2025-24203 |
The issue was addressed with improved checks
|
5.0
Moyenne
|
31 mars 2025 |
| CVE-2025-31191 |
This issue was addressed through improved state management
|
5.5
Moyenne
|
31 mars 2025 |
| CVE-2025-24238 |
A logic issue was addressed with improved checks
|
9.8
Critique
|
31 mars 2025 |
| CVE-2025-30447 |
The issue was resolved by sanitizing logging
|
5.5
Moyenne
|
31 mars 2025 |
| CVE-2025-24214 |
A privacy issue was addressed by not logging contents of text fields
|
5.5
Moyenne
|
31 mars 2025 |
| CVE-2025-24097 |
A permissions issue was addressed with additional restrictions
|
5.0
Moyenne
|
31 mars 2025 |
| CVE-2025-24243 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
31 mars 2025 |