| CVE-2026-64778 |
The issue was addressed with improved checks
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-64715 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-65349 |
An out-of-bounds read was addressed with improved input validation
|
6.6
Medium
|
Aug 17, 2026 |
| CVE-2026-43813 |
A validation issue was addressed with improved input sanitization
|
7.1
High
|
Jul 27, 2026 |
| CVE-2026-64721 |
This issue was addressed through improved state management
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64740 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
9.3
Critical
|
Jul 27, 2026 |
| CVE-2026-43673 |
The issue was addressed with improved memory handling
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43799 |
A use after free issue was addressed with improved memory management
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64716 |
The issue was addressed with improved memory handling
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-64741 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64700 |
A use after free issue was addressed with improved memory management
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64720 |
A race condition was addressed with improved state handling
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43812 |
A use after free issue was addressed with improved memory management
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43730 |
A permissions issue was addressed with additional restrictions
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-28931 |
A buffer overflow was addressed with improved bounds checking
|
8.8
High
|
Jul 27, 2026 |
| CVE-2026-43803 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64766 |
An integer overflow was addressed with improved input validation
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-64770 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64727 |
A type confusion issue was addressed with improved memory handling
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64726 |
The issue was addressed with improved memory handling
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64771 |
A buffer overflow was addressed with improved bounds checking
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43814 |
A use after free issue was addressed with improved memory management
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64730 |
The issue was addressed with improved UI
|
6.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43711 |
A memory corruption issue was addressed with improved memory handling
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43770 |
A race condition was addressed with additional validation
|
4.7
Medium
|
Jul 27, 2026 |