| 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 |
| CVE-2026-43743 |
A race condition was addressed with improved state handling
|
4.7
Medium
|
Jun 29, 2026 |
| CVE-2026-43722 |
The issue was addressed with improved input sanitization
|
5.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43734 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43718 |
A stack overflow was addressed with improved input validation
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-28979 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43735 |
The issue was addressed with improved checks
|
8.1
High
|
Jun 29, 2026 |
| CVE-2026-43703 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43715 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Jun 29, 2026 |
| CVE-2026-43742 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2025-30431 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-24268 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-43339 |
An access issue was addressed with additional sandbox restrictions
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-46293 |
This issue was addressed with improved handling of symlinks
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-46315 |
A permissions issue was addressed with additional restrictions
|
7.5
High
|
Jun 11, 2026 |
| CVE-2025-31272 |
The issue was addressed with improved checks
|
7.8
High
|
Jun 11, 2026 |
| CVE-2025-30459 |
A privacy issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-24165 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Jun 11, 2026 |
| CVE-2025-24284 |
This issue was addressed with improved checks to prevent unauthorized actions
|
8.8
High
|
Jun 11, 2026 |