| CVE-2026-28987 |
A logging issue was addressed with improved data redaction
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28991 |
An out-of-bounds read was addressed with improved bounds checking
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28929 |
A logic issue was addressed with improved checks
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28964 |
An inconsistent user interface issue was addressed with improved state management
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28883 |
A use-after-free issue was addressed with improved memory management
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28972 |
An out-of-bounds write issue was addressed with improved input validation
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28860 |
The issue was addressed with improved input validation
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28965 |
A privacy issue was addressed with improved checks
|
7.5
High
|
May 11, 2026 |
| CVE-2026-43656 |
An out-of-bounds write issue was addressed with improved input validation
|
7.3
High
|
May 11, 2026 |
| CVE-2026-28990 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28986 |
A race condition was addressed with additional validation
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28969 |
A use after free issue was addressed with improved memory management
|
7.5
High
|
May 11, 2026 |
| CVE-2026-43660 |
A validation issue was addressed with improved logic
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28904 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28953 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28958 |
This issue was addressed with improved data protection
|
5.5
Medium
|
May 11, 2026 |
| CVE-2026-28962 |
This issue was addressed with improved access restrictions
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28974 |
This issue was addressed with improved checks to prevent unauthorized actions
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28954 |
A file quarantine bypass was addressed with additional checks
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28903 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28846 |
A buffer overflow was addressed with improved bounds checking
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28942 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28996 |
A race condition was addressed with additional validation
|
5.5
Medium
|
May 11, 2026 |
| CVE-2026-28943 |
A logging issue was addressed with improved data redaction
|
7.5
High
|
May 11, 2026 |
| CVE-2026-43666 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.2
Medium
|
May 11, 2026 |