| CVE-2026-112566 |
A null pointer dereference was addressed with improved validation
|
4.6
Medium
|
Oct 26, 2026 |
| CVE-2026-112474 |
A use-after-free issue was addressed with improved memory management
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-112571 |
A memory initialization issue was addressed with improved memory handling
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-86992 |
The issue was addressed with improved memory handling
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112619 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112567 |
This issue was addressed with improved checks
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112459 |
A race condition was addressed with improved state handling
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-86988 |
The issue was addressed with improved checks
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112615 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-113907 |
A buffer overflow issue was addressed with improved memory handling
|
6.1
Medium
|
Oct 26, 2026 |
| CVE-2026-113950 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.4
Medium
|
Oct 26, 2026 |
| CVE-2026-112455 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112697 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112678 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Oct 26, 2026 |
| 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-86872 |
A logic issue was addressed with improved state 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 |