| CVE-2026-28828 |
A permissions issue was addressed by removing the vulnerable code
|
5.3
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-28824 |
An authorization issue was addressed with improved state management
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28832 |
An out-of-bounds read was addressed with improved bounds checking
|
8.4
High
|
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-28881 |
A privacy issue was addressed by moving sensitive data
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28839 |
The issue was addressed with improved checks
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28878 |
A privacy issue was addressed by removing sensitive data
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28842 |
The issue was addressed with improved bounds checks
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28862 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-20697 |
A permissions issue was addressed with additional restrictions
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28835 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28823 |
A path handling issue was addressed with improved validation
|
4.9
Medium
|
Mar 25, 2026 |
| CVE-2026-20639 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28818 |
A logging issue was addressed with improved data redaction
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28859 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28822 |
A type confusion issue was addressed with improved memory handling
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-28834 |
A race condition was addressed with improved state handling
|
5.1
Medium
|
Mar 25, 2026 |
| CVE-2026-28855 |
A permissions issue was addressed with additional restrictions
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28879 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28838 |
A permissions issue was addressed with additional sandbox restrictions
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-20622 |
A privacy issue was addressed with improved handling of temporary files
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28880 |
A permissions issue was addressed with additional restrictions
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28817 |
A race condition was addressed with improved state handling
|
8.1
High
|
Mar 25, 2026 |