| CVE-2026-43734 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43718 |
A stack overflow was addressed with improved input validation
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-28979 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43735 |
The issue was addressed with improved checks
|
8.1
High
|
Jun 29, 2026 |
| CVE-2026-43715 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Jun 29, 2026 |
| CVE-2026-43742 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-28917 |
The issue was addressed with improved input validation
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28901 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28907 |
The issue was addressed with improved input validation
|
8.1
High
|
May 11, 2026 |
| CVE-2026-28946 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28971 |
The issue was addressed with improved UI handling
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28947 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
May 11, 2026 |
| CVE-2026-43658 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28905 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28913 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28944 |
The issue was addressed with improved memory handling
|
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-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-28903 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
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-28902 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
May 11, 2026 |