| CVE-2026-28968 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84551 |
A logic issue was addressed with improved validation
|
4.4
Medium
|
Sep 14, 2026 |
| CVE-2026-64752 |
A memory corruption issue was addressed by removing the vulnerable code
|
7.3
High
|
Sep 14, 2026 |
| CVE-2026-86887 |
A privacy issue was addressed by removing sensitive data
|
3.3
Low
|
Sep 14, 2026 |
| CVE-2026-65358 |
A race condition was addressed with improved state handling
|
4.7
Medium
|
Sep 14, 2026 |
| CVE-2026-84571 |
A buffer overflow was addressed with improved bounds checking
|
4.3
Medium
|
Sep 14, 2026 |
| CVE-2026-84526 |
An out-of-bounds write issue was addressed with improved bounds checking
|
4.3
Medium
|
Sep 14, 2026 |
| CVE-2026-84530 |
An information disclosure issue was addressed with improved memory management
|
3.3
Low
|
Sep 14, 2026 |
| CVE-2026-20683 |
An authentication issue was addressed with improved state management
|
7.1
High
|
Sep 14, 2026 |
| CVE-2026-84635 |
A logic issue was addressed with improved state management
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84622 |
A memory initialization issue was addressed with improved memory handling
|
6.2
Medium
|
Sep 14, 2026 |
| CVE-2026-43695 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84527 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-65359 |
An out-of-bounds read was addressed with improved bounds checking
|
7.1
High
|
Sep 14, 2026 |
| CVE-2026-84507 |
A race condition was addressed with improved state handling
|
7.8
High
|
Sep 14, 2026 |
| CVE-2026-64753 |
A permissions issue was addressed by removing the vulnerable code
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84546 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.4
High
|
Sep 14, 2026 |
| CVE-2026-84511 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.8
High
|
Sep 14, 2026 |
| CVE-2026-84497 |
A buffer overflow was addressed with improved size validation
|
7.8
High
|
Sep 14, 2026 |
| CVE-2026-84602 |
A type confusion issue was addressed with improved checks
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-65355 |
An information disclosure issue was addressed with improved state management
|
4.3
Medium
|
Sep 14, 2026 |
| CVE-2026-84609 |
A permissions issue was addressed with improved path validation
|
9.8
Critical
|
Sep 14, 2026 |
| CVE-2026-84561 |
A double free issue was addressed with improved memory management
|
9.8
Critical
|
Sep 14, 2026 |
| CVE-2026-28935 |
The issue was addressed with improved memory handling
|
7.5
High
|
Sep 14, 2026 |
| CVE-2026-84625 |
A permissions issue was addressed with additional sandbox restrictions
|
9.1
Critical
|
Sep 14, 2026 |