| 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-28963 |
A privacy issue was addressed by removing the vulnerable code
|
4.6
Medium
|
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-2026-28950 |
A logging issue was addressed with improved data redaction
|
6.2
Medium
|
Apr 22, 2026 |
| CVE-2025-43210 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.3
Medium
|
Apr 2, 2026 |
| CVE-2025-43202 |
This issue was addressed with improved memory handling
|
8.8
High
|
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-28833 |
A permissions issue was addressed with additional restrictions
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-20668 |
A logging issue was addressed with improved data redaction
|
5.5
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-2025-43534 |
A path handling issue was addressed with improved validation
|
6.8
Medium
|
Mar 25, 2026 |
| CVE-2026-28868 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-20664 |
The issue was addressed with improved memory handling
|
4.3
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 |
| CVE-2026-20686 |
This issue was addressed with improved input validation
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-20690 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28865 |
An authentication issue was addressed with improved state management
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28878 |
A privacy issue was addressed by removing sensitive data
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28874 |
The issue was addressed with improved checks
|
7.5
High
|
Mar 25, 2026 |