| 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-28974 |
This issue was addressed with improved checks to prevent unauthorized actions
|
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 |
| CVE-2026-28902 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28847 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 11, 2026 |
| CVE-2026-28955 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 11, 2026 |
| CVE-2026-28918 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28959 |
A buffer overflow was addressed with improved bounds checking
|
7.5
High
|
May 11, 2026 |
| CVE-2025-43210 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.3
Medium
|
Apr 2, 2026 |
| CVE-2026-28864 |
This issue was addressed with improved permissions checking
|
3.3
Low
|
Mar 25, 2026 |
| CVE-2026-20691 |
An authorization issue was addressed with improved state management
|
4.3
Medium
|
Mar 25, 2026 |
| CVE-2026-20687 |
A use after free issue was addressed with improved memory management
|
7.1
High
|
Mar 25, 2026 |
| CVE-2026-28868 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28852 |
A stack overflow was addressed with improved input validation
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-20665 |
This issue was addressed through improved state management
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28886 |
A null pointer dereference was addressed with improved input validation
|
5.9
Medium
|
Mar 25, 2026 |