| CVE-2026-65347 |
The issue was addressed with improved checks
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-43795 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65330 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-65340 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65337 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64788 |
The issue was addressed with improved memory handling
|
5.4
Medium
|
Aug 17, 2026 |
| CVE-2026-65336 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64784 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65341 |
The issue was addressed with improved memory handling
|
5.4
Medium
|
Aug 17, 2026 |
| CVE-2026-28984 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64787 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-65339 |
A logic issue was addressed with improved checks
|
5.0
Medium
|
Aug 17, 2026 |
| CVE-2026-65335 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65334 |
A memory corruption issue was addressed with improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65338 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65343 |
A use after free issue was addressed with improved memory management
|
7.5
High
|
Aug 17, 2026 |
| CVE-2026-65333 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64778 |
The issue was addressed with improved checks
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-43667 |
A reachable assertion was addressed with improved input validation
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-64781 |
The issue was addressed with improved input validation
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64715 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-65329 |
An authentication issue was addressed with improved state management
|
5.9
Medium
|
Aug 17, 2026 |
| CVE-2026-64780 |
The issue was addressed with improved checks
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64779 |
A memory corruption vulnerability was addressed with improved locking
|
3.1
Low
|
Aug 17, 2026 |
| CVE-2026-65332 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |