| CVE-2026-64758 |
The issue was addressed with improved bounds checks
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43775 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64693 |
A type confusion issue was addressed with improved checks
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64739 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.8
High
|
Jul 27, 2026 |
| CVE-2026-43763 |
A permissions issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-28981 |
A buffer overflow was addressed with improved bounds checking
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-64703 |
A use after free issue was addressed with improved memory management
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43759 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64754 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43758 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64702 |
An access issue was addressed with additional sandbox restrictions
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-64743 |
An authorization issue was addressed with improved state management
|
6.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64692 |
An out-of-bounds read was addressed with improved bounds checking
|
7.1
High
|
Jul 27, 2026 |
| CVE-2026-64738 |
A permissions issue was addressed with additional restrictions
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43723 |
A path handling issue was addressed with improved validation
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43774 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43754 |
This issue was addressed with improved redaction of sensitive information
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64718 |
A use-after-free issue was addressed with improved memory management
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64734 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43781 |
A race condition was addressed with improved state handling
|
4.7
Medium
|
Jul 27, 2026 |
| CVE-2026-43806 |
A denial of service issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43693 |
A race condition was addressed with improved state handling
|
7.0
High
|
Jul 27, 2026 |
| CVE-2026-64763 |
An out-of-bounds write issue was addressed by removing the vulnerable code
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43739 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43810 |
The issue was addressed with improved memory handling
|
9.8
Critical
|
Jul 27, 2026 |