| CVE-2026-84599 |
The issue was addressed with improved memory handling
|
4.4
Medium
|
Oct 26, 2026 |
| CVE-2026-86962 |
A double free issue was addressed with improved memory management
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86975 |
An out-of-bounds read was addressed with improved bounds checking
|
4.3
Medium
|
Oct 20, 2026 |
| CVE-2026-86957 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86953 |
An out-of-bounds write issue was addressed with improved bounds checking
|
4.6
Medium
|
Oct 20, 2026 |
| CVE-2026-86918 |
An out-of-bounds write issue was addressed with improved bounds checking
|
4.3
Medium
|
Oct 20, 2026 |
| CVE-2026-86913 |
A use after free issue was addressed with improved memory management
|
5.4
Medium
|
Oct 20, 2026 |
| CVE-2026-84613 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.5
Medium
|
Oct 20, 2026 |
| CVE-2026-84582 |
A privacy issue was addressed with improved access restrictions
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-65409 |
A type confusion issue was addressed with improved memory handling
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-43686 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Sep 14, 2026 |
| CVE-2026-84575 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
High
|
Sep 14, 2026 |
| CVE-2026-65405 |
A memory initialization issue was addressed with improved memory handling
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-64717 |
A race condition was addressed with improved state handling
|
6.3
Medium
|
Sep 14, 2026 |
| CVE-2026-86895 |
An information disclosure issue was addressed with improved state management
|
7.5
High
|
Sep 14, 2026 |
| CVE-2026-84611 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.3
High
|
Sep 14, 2026 |
| CVE-2026-84492 |
A race condition was addressed with improved state handling
|
4.7
Medium
|
Sep 14, 2026 |
| CVE-2026-84607 |
A race condition was addressed with improved state management
|
7.8
High
|
Sep 14, 2026 |
| CVE-2026-84596 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84597 |
An out-of-bounds read issue was addressed with improved input validation
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-43664 |
This issue was addressed with improved data protection
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-43808 |
A use-after-free issue was addressed with improved memory management
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-43737 |
An authorization issue was addressed with improved validation
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-86882 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-43687 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Sep 14, 2026 |