| CVE-2025-46303 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20617 |
A race condition was addressed with improved state handling
|
7.0
Élevée
|
11 févr. 2026 |
| CVE-2026-20641 |
A privacy issue was addressed with improved checks
|
7.1
Élevée
|
11 févr. 2026 |
| CVE-2025-46302 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20650 |
A denial-of-service issue was addressed with improved validation
|
7.5
Élevée
|
11 févr. 2026 |
| CVE-2026-20611 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
Élevée
|
11 févr. 2026 |
| CVE-2025-46305 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20627 |
An issue existed in the handling of environment variables
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20671 |
A logic issue was addressed with improved checks
|
3.1
Faible
|
11 févr. 2026 |
| CVE-2025-46304 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20667 |
A logic issue was addressed with improved checks
|
8.8
Élevée
|
11 févr. 2026 |
| CVE-2025-46298 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
9 janv. 2026 |
| CVE-2025-46299 |
A memory initialization issue was addressed with improved memory handling
|
4.3
Moyenne
|
9 janv. 2026 |
| CVE-2025-46279 |
A permissions issue was addressed with additional restrictions
|
9.8
Critique
|
17 déc. 2025 |
| CVE-2025-43533 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
17 déc. 2025 |
| CVE-2025-43529 |
Exploitée
Apple Multiple Products Use-After-Free WebKit Vulnerability
|
8.8
Élevée
|
17 déc. 2025 |
| CVE-2025-46288 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
17 déc. 2025 |
| CVE-2025-43531 |
A race condition was addressed with improved state handling
|
3.1
Faible
|
17 déc. 2025 |
| CVE-2025-46277 |
A logging issue was addressed with improved data redaction
|
5.5
Moyenne
|
17 déc. 2025 |
| CVE-2025-43518 |
A logic issue was addressed with improved checks
|
3.3
Faible
|
12 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-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 |