| CVE-2026-64733 |
This issue was addressed with improved data protection
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43753 |
An out-of-bounds read was addressed with improved bounds checking
|
4.6
Moyenne
|
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-64749 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64732 |
This issue was addressed through improved state management
|
4.6
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-43729 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
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-43748 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critique
|
27 juil. 2026 |
| CVE-2026-43733 |
The issue was addressed with improved memory handling
|
7.8
Élevée
|
27 juil. 2026 |
| CVE-2026-64769 |
An out-of-bounds write issue was addressed with improved bounds checking
|
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-43811 |
A race condition was addressed with improved checks
|
4.7
Moyenne
|
27 juil. 2026 |
| CVE-2026-64723 |
A logic issue was addressed with improved checks
|
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-43738 |
The issue was addressed with improved memory handling
|
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-64762 |
An out-of-bounds read was addressed with improved bounds checking
|
9.8
Critique
|
27 juil. 2026 |