| CVE-2026-20670 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-20688 |
A path handling issue was addressed with improved validation
|
9.3
Critical
|
Mar 25, 2026 |
| CVE-2026-28892 |
A permissions issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28867 |
This issue was addressed with improved authentication
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-28888 |
A race condition was addressed with improved state handling
|
5.1
Medium
|
Mar 25, 2026 |
| CVE-2026-20692 |
A privacy issue was addressed with improved handling of user preferences
|
5.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28826 |
A logic issue was addressed with improved restrictions
|
4.0
Medium
|
Mar 25, 2026 |
| CVE-2026-28871 |
A logic issue was addressed with improved checks
|
4.3
Medium
|
Mar 25, 2026 |
| CVE-2026-20684 |
A permissions issue was addressed with additional restrictions
|
3.3
Low
|
Mar 25, 2026 |
| CVE-2026-20651 |
A privacy issue was addressed with improved handling of temporary files
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-20643 |
A cross-origin issue in the Navigation API was addressed with improved input validation
|
5.4
Medium
|
Mar 17, 2026 |
| CVE-2023-43010 |
The issue was addressed with improved memory handling
|
8.8
High
|
Mar 12, 2026 |
| CVE-2026-20629 |
A privacy issue was addressed with improved handling of temporary files
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20644 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20652 |
The issue was addressed with improved memory handling
|
7.5
High
|
Feb 11, 2026 |
| CVE-2026-20605 |
The issue was addressed with improved memory handling
|
4.6
Medium
|
Feb 11, 2026 |
| CVE-2026-20625 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20648 |
A privacy issue was addressed by moving sensitive data to a protected location
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20609 |
The issue was addressed with improved memory handling
|
4.4
Medium
|
Feb 11, 2026 |
| CVE-2026-20608 |
This issue was addressed through improved state management
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20624 |
An injection issue was addressed with improved validation
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20649 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20673 |
A logic issue was addressed with improved checks
|
5.3
Medium
|
Feb 11, 2026 |
| CVE-2025-46310 |
This issue was addressed through improved state management
|
6.0
Medium
|
Feb 11, 2026 |
| CVE-2026-20653 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
5.5
Medium
|
Feb 11, 2026 |