| CVE-2026-64713 |
This issue was addressed with improved checks
|
8.1
Élevée
|
27 juil. 2026 |
| CVE-2026-64725 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.1
Élevée
|
27 juil. 2026 |
| CVE-2026-43817 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-39877 |
A memory corruption issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43801 |
This issue was addressed with improved checks
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64764 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43769 |
An integer overflow was addressed with improved input validation
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64733 |
This issue was addressed with improved data protection
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-64709 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-28973 |
An integer overflow was addressed with improved input validation
|
8.6
Élevée
|
27 juil. 2026 |
| CVE-2026-43744 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-43800 |
An information disclosure issue was addressed by removing the vulnerable code
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64765 |
An integer overflow was addressed with improved input validation
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-43816 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-64724 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
27 juil. 2026 |
| CVE-2026-28928 |
A use after free issue was addressed with improved memory management
|
9.8
Critique
|
27 juil. 2026 |
| 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-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-43714 |
The issue was addressed with improved input sanitization
|
5.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 |