| CVE-2026-43700 |
A cross-origin issue was addressed with improved tracking of security origins
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43716 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43720 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43721 |
This issue was addressed through improved state management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-39872 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43717 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43740 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43701 |
The issue was addressed with improved checks
|
7.1
High
|
Jun 29, 2026 |
| CVE-2026-43663 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43726 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43746 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43707 |
A memory corruption issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43727 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43731 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Jun 29, 2026 |
| CVE-2026-43732 |
A path handling issue was addressed with improved validation
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43708 |
The issue was addressed with improved input validation
|
4.3
Medium
|
Jun 29, 2026 |
| CVE-2026-43712 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43745 |
An out-of-bounds write issue was addressed with improved input validation
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43704 |
A use-after-free issue was addressed with improved memory management
|
5.3
Medium
|
Jun 29, 2026 |
| CVE-2026-43705 |
A type confusion issue was addressed with improved checks
|
8.8
High
|
Jun 29, 2026 |
| CVE-2026-43713 |
A permissions issue was addressed with additional restrictions
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43709 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43699 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43676 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43725 |
The issue was addressed with improved input validation
|
7.1
High
|
Jun 29, 2026 |