| CVE-2026-112642 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
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-112639 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112414 |
A stack overflow was addressed with improved input validation
|
6.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-113897 |
This issue was addressed by removing the vulnerable code
|
10.0
Critical
|
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-86922 |
A type confusion issue was addressed with improved state management
|
8.8
High
|
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-86919 |
A stack overflow was addressed with improved input validation
|
8.8
High
|
Oct 20, 2026 |
| CVE-2026-86921 |
A permissions issue was addressed with improved validation
|
6.2
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-84508 |
This issue was addressed with improved validation of the caller's access
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-28850 |
An authorization issue was addressed with improved state management
|
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-86876 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.2
Medium
|
Sep 14, 2026 |