| CVE-2026-112618 |
An access issue was addressed with improved access restrictions
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112659 |
A type confusion issue was addressed with improved memory handling
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112658 |
This issue was addressed with improved input validation
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112571 |
A memory initialization issue was addressed with improved memory handling
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-86880 |
This issue was addressed with additional entitlement checks
|
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-112623 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-84595 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-64759 |
An integer overflow was addressed with improved input validation
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112654 |
A use-after-free issue was addressed with improved memory management
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-86971 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-86988 |
The issue was addressed with improved checks
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112479 |
An out-of-bounds read was addressed with improved bounds checking
|
5.2
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-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-112707 |
A privacy issue was addressed by moving sensitive data to a protected location
|
3.3
Low
|
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-112547 |
A type confusion issue was addressed with improved checks
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112681 |
This issue was addressed with additional entitlement checks
|
5.5
Medium
|
Oct 26, 2026 |