| CVE-2026-86925 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-84627 |
A buffer overflow was addressed with improved bounds checking
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-86972 |
A buffer overflow was addressed with improved size validation
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-113912 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.1
High
|
Oct 26, 2026 |
| CVE-2026-86964 |
A null pointer dereference was addressed with improved input validation
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-113904 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112616 |
An authorization issue was addressed with improved access control
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112456 |
An out-of-bounds write issue was addressed with improved input validation
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-112682 |
An input validation issue was addressed with improved input validation
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-113949 |
A type confusion issue was addressed with improved state management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-86991 |
A buffer overflow was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-65385 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-113908 |
A privacy issue was addressed by removing sensitive data
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-86968 |
An access issue was addressed with improved access control
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112476 |
An out-of-bounds read was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-86987 |
An authorization issue was addressed with improved entitlement checks
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112698 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-113898 |
A logging issue was addressed with improved data redaction
|
3.3
Low
|
Oct 26, 2026 |
| CVE-2026-65350 |
A use-after-free issue was addressed with improved memory management
|
7.1
High
|
Oct 26, 2026 |
| CVE-2026-112620 |
A denial-of-service issue was addressed with improved input validation
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112621 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112676 |
This issue was addressed with additional entitlement checks
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112699 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-84493 |
An authentication issue was addressed with improved state management
|
4.4
Medium
|
Oct 26, 2026 |
| CVE-2026-112660 |
An authorization issue was addressed with improved state management
|
3.3
Low
|
Oct 26, 2026 |