| CVE-2026-28847 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
11 mai 2026 |
| CVE-2026-28955 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
11 mai 2026 |
| CVE-2026-20691 |
An authorization issue was addressed with improved state management
|
4.3
Moyenne
|
25 mars 2026 |
| CVE-2026-20664 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
25 mars 2026 |
| CVE-2026-20665 |
This issue was addressed through improved state management
|
6.5
Moyenne
|
25 mars 2026 |
| CVE-2026-28859 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
25 mars 2026 |
| CVE-2026-28861 |
A logic issue was addressed with improved state management
|
4.3
Moyenne
|
25 mars 2026 |
| CVE-2026-28857 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
25 mars 2026 |
| CVE-2026-28871 |
A logic issue was addressed with improved checks
|
4.3
Moyenne
|
25 mars 2026 |
| CVE-2026-20643 |
A cross-origin issue in the Navigation API was addressed with improved input validation
|
5.4
Moyenne
|
17 mars 2026 |
| CVE-2023-43010 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
12 mars 2026 |
| CVE-2026-20644 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20652 |
The issue was addressed with improved memory handling
|
7.5
Élevée
|
11 févr. 2026 |
| CVE-2026-20608 |
This issue was addressed through improved state management
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20635 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
11 févr. 2026 |
| CVE-2026-20660 |
A path handling issue was addressed with improved logic
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20676 |
This issue was addressed through improved state management
|
4.3
Moyenne
|
11 févr. 2026 |
| CVE-2026-20656 |
A logic issue was addressed with improved validation
|
3.3
Faible
|
11 févr. 2026 |
| CVE-2026-20636 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
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-43535 |
The issue was addressed with improved memory handling
|
4.3
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-43531 |
A race condition was addressed with improved state handling
|
3.1
Faible
|
17 déc. 2025 |