| CVE-2026-86979 |
A privacy issue was addressed with improved checks
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86981 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Oct 20, 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-86959 |
An input validation issue was addressed with improved input validation
|
4.3
Medium
|
Oct 20, 2026 |
| CVE-2026-86961 |
A race condition was addressed with additional validation
|
7.8
High
|
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-86933 |
A permissions issue was addressed with additional sandbox restrictions
|
3.3
Low
|
Oct 20, 2026 |
| CVE-2026-86935 |
This issue was addressed by removing additional entitlements
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86940 |
This issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86944 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
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-86928 |
A path handling issue was addressed with improved validation
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86932 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
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-86914 |
An information disclosure issue was addressed with improved state management
|
5.5
Medium
|
Oct 20, 2026 |
| CVE-2026-86915 |
A race condition was addressed with improved locking
|
4.7
Medium
|
Oct 20, 2026 |
| CVE-2026-86907 |
An authorization issue was addressed with improved entitlement checks
|
4.4
Medium
|
Oct 20, 2026 |
| CVE-2026-86871 |
An integer underflow was addressed with improved input validation
|
5.9
Medium
|
Oct 20, 2026 |
| CVE-2026-86868 |
An authentication issue was addressed with improved state management
|
9.1
Critical
|
Oct 20, 2026 |
| CVE-2026-84613 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.5
Medium
|
Oct 20, 2026 |