| CVE-2026-86968 |
An access issue was addressed with improved access control
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112533 |
An authorization issue was addressed with improved state management
|
5.5
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-112708 |
A race condition was addressed with improved locking
|
5.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112421 |
A race condition was addressed with improved handling of symbolic links
|
4.7
Medium
|
Oct 26, 2026 |
| CVE-2026-43736 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112548 |
A use after free issue was addressed with improved memory management
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-112677 |
An authorization issue was addressed with improved access control
|
7.8
High
|
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-112508 |
An out-of-bounds read was addressed with improved bounds checking
|
7.1
High
|
Oct 26, 2026 |
| CVE-2026-113899 |
The issue was addressed with improved checks
|
5.5
Medium
|
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-84539 |
An out-of-bounds write issue was addressed with improved bounds checking
|
9.8
Critical
|
Oct 26, 2026 |
| CVE-2026-112660 |
An authorization issue was addressed with improved state management
|
3.3
Low
|
Oct 26, 2026 |
| CVE-2026-84610 |
A file quarantine bypass was addressed with additional checks
|
5.5
Medium
|
Oct 26, 2026 |
| CVE-2026-86945 |
This issue was addressed with improved checks
|
7.1
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-112565 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112532 |
The issue was addressed with improved memory handling
|
7.8
High
|
Oct 26, 2026 |
| CVE-2026-86969 |
An out-of-bounds write was addressed with improved input validation
|
7.5
High
|
Oct 26, 2026 |