| 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-20672 |
An information disclosure issue was addressed with improved privacy controls
|
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-64691 |
A buffer overflow was addressed with improved size validation
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43673 |
The issue was addressed with improved memory handling
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-64783 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Jul 27, 2026 |
| CVE-2026-43665 |
This issue was addressed with additional entitlement checks
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43809 |
An out-of-bounds read was addressed with improved bounds checking
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-43777 |
This issue was addressed with improved input validation
|
7.5
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-28900 |
A file quarantine bypass was addressed with additional checks
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43776 |
A buffer overflow was addressed with improved bounds checking
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-43672 |
An authorization issue was addressed with improved state management
|
7.1
High
|
Jul 27, 2026 |
| CVE-2026-43760 |
An access issue was addressed with improved access restrictions
|
8.6
High
|
Jul 27, 2026 |
| CVE-2026-64716 |
The issue was addressed with improved memory handling
|
7.8
High
|
Jul 27, 2026 |
| CVE-2026-28982 |
A race condition was addressed with improved locking
|
9.8
Critical
|
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-64757 |
A memory corruption issue was addressed with improved state management
|
8.8
High
|
Jul 27, 2026 |
| CVE-2026-64720 |
A race condition was addressed with improved state handling
|
9.8
Critical
|
Jul 27, 2026 |
| CVE-2026-28849 |
The issue was addressed with improved checks
|
5.5
Medium
|
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-43804 |
This issue was addressed through improved state management
|
6.5
Medium
|
Jul 27, 2026 |
| CVE-2026-43756 |
A logic issue was addressed with improved validation
|
5.5
Medium
|
Jul 27, 2026 |
| CVE-2026-64707 |
A permissions issue was addressed with improved validation
|
5.5
Medium
|
Jul 27, 2026 |