| CVE-2026-64728 |
A permissions issue was addressed with improved validation
|
6.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-43796 |
This issue was addressed with improved data protection
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64774 |
An integer overflow was addressed with improved input validation
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43807 |
A buffer overflow was addressed with improved bounds checking
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43780 |
An integer overflow was addressed with improved input validation
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64735 |
An inconsistent user interface issue was addressed with improved state management
|
6.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64719 |
An out-of-bounds access issue was addressed with improved bounds checking
|
8.1
Élevée
|
27 juil. 2026 |
| CVE-2026-64758 |
The issue was addressed with improved bounds checks
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64693 |
A type confusion issue was addressed with improved checks
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64739 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64742 |
This issue was addressed by using HTTPS when sending information over the network
|
6.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64754 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64743 |
An authorization issue was addressed with improved state management
|
6.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64692 |
An out-of-bounds read was addressed with improved bounds checking
|
7.1
Élevée
|
27 juil. 2026 |
| CVE-2026-43723 |
A path handling issue was addressed with improved validation
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64718 |
A use-after-free issue was addressed with improved memory management
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64763 |
An out-of-bounds write issue was addressed by removing the vulnerable code
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43739 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-43810 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64775 |
A memory initialization issue was addressed with improved memory handling
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43778 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43700 |
A cross-origin issue was addressed with improved tracking of security origins
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-43720 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juin 2026 |
| CVE-2026-39868 |
This issue was addressed with improved input validation
|
9.1
Critique
|
29 juin 2026 |
| CVE-2026-43721 |
This issue was addressed through improved state management
|
6.5
Moyenne
|
29 juin 2026 |