| 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-112476 |
An out-of-bounds read was addressed with improved bounds checking
|
7.5
High
|
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-112637 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112477 |
A race condition was addressed with improved locking
|
7.0
High
|
Oct 26, 2026 |
| CVE-2026-112416 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112705 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112640 |
A use-after-free issue was addressed with improved memory management
|
7.6
High
|
Oct 26, 2026 |
| CVE-2026-112656 |
An out-of-bounds read was addressed with improved bounds checking
|
3.3
Low
|
Oct 26, 2026 |
| CVE-2026-86978 |
This issue was addressed with improved checks
|
3.3
Low
|
Oct 26, 2026 |
| CVE-2026-112466 |
An out-of-bounds read was addressed with improved input validation
|
7.1
High
|
Oct 26, 2026 |
| CVE-2026-112470 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-112626 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-86954 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112485 |
The issue was addressed with improved memory handling
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-112606 |
A type confusion issue was addressed with improved memory handling
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112515 |
An out-of-bounds read was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112684 |
This issue was addressed through improved state management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112692 |
This issue was addressed with additional entitlement checks
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112446 |
This issue was addressed with additional entitlement checks
|
Not rated
|
Oct 26, 2026 |