| CVE-2026-43813 |
A validation issue was addressed with improved input sanitization
|
7.1
Élevée
|
27 juil. 2026 |
| CVE-2026-64721 |
This issue was addressed through improved state management
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-43673 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64783 |
A use-after-free issue was addressed with improved memory management
|
8.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43799 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64716 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64741 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64700 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64757 |
A memory corruption issue was addressed with improved state management
|
8.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64720 |
A race condition was addressed with improved state handling
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64746 |
An authorization issue was addressed with improved validation
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43730 |
A permissions issue was addressed with additional restrictions
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-28931 |
A buffer overflow was addressed with improved bounds checking
|
8.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43803 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64766 |
An integer overflow was addressed with improved input validation
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64726 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43814 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64730 |
The issue was addressed with improved UI
|
6.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-43711 |
A memory corruption issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-28896 |
The issue was addressed with improved memory handling
|
7.7
Élevée
|
27 juil. 2026 |
| CVE-2026-43822 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64747 |
A buffer overflow was addressed with improved size validation
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64751 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64729 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43821 |
An access issue was addressed with improved access restrictions
|
6.5
Moyenne
|
27 juil. 2026 |