| CVE-2026-20606 |
This issue was addressed by removing the vulnerable code
|
7.1
Élevée
|
11 févr. 2026 |
| CVE-2025-46306 |
The issue was addressed with improved bounds checks
|
5.5
Moyenne
|
28 janv. 2026 |
| CVE-2025-46316 |
An out-of-bounds read was addressed with improved input validation
|
4.3
Moyenne
|
28 janv. 2026 |
| CVE-2025-43508 |
A logging issue was addressed with improved data redaction
|
5.5
Moyenne
|
16 janv. 2026 |
| CVE-2024-44210 |
This issue was addressed with improved permissions checking
|
3.3
Faible
|
16 janv. 2026 |
| CVE-2024-44238 |
The issue was addressed with improved bounds checks
|
7.8
Élevée
|
16 janv. 2026 |
| CVE-2025-46297 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
9 janv. 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-43514 |
The issue was addressed with improved handling of caches
|
5.5
Moyenne
|
17 déc. 2025 |
| CVE-2025-46281 |
A logic issue was addressed with improved checks
|
8.4
Élevée
|
17 déc. 2025 |
| CVE-2025-46278 |
The issue was addressed with improved handling of caches
|
5.0
Moyenne
|
17 déc. 2025 |
| CVE-2025-46279 |
A permissions issue was addressed with additional restrictions
|
9.8
Critique
|
17 déc. 2025 |
| CVE-2025-43535 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
17 déc. 2025 |
| CVE-2025-46291 |
A logic issue was addressed with improved validation
|
5.5
Moyenne
|
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-43526 |
This issue was addressed with improved URL validation
|
9.8
Critique
|
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-43536 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
17 déc. 2025 |
| CVE-2025-43428 |
A configuration issue was addressed with additional restrictions
|
9.8
Critique
|
17 déc. 2025 |
| CVE-2025-46283 |
A logic issue was addressed with improved validation
|
5.5
Moyenne
|
17 déc. 2025 |
| CVE-2025-43541 |
A type confusion issue was addressed with improved state handling
|
4.3
Moyenne
|
17 déc. 2025 |
| CVE-2025-43501 |
A buffer overflow issue was addressed with improved memory handling
|
4.3
Moyenne
|
17 déc. 2025 |