| CVE-2026-28913 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-43661 |
A buffer overflow 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-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-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-28925 |
A buffer overflow was addressed with improved bounds checking
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28924 |
A race condition was addressed with improved handling of symbolic links
|
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-28908 |
A denial of service issue was addressed by removing the vulnerable code
|
7.5
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-39871 |
A path handling issue was addressed with improved logic
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28919 |
A consistency issue was addressed with improved state handling
|
7.8
High
|
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-28923 |
A logging issue was addressed with improved data redaction
|
8.8
High
|
May 11, 2026 |