| CVE-2026-20690 |
An out-of-bounds access issue was addressed with improved bounds checking
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28865 |
An authentication issue was addressed with improved state management
|
7.5
High
|
Mar 25, 2026 |
| CVE-2026-28878 |
A privacy issue was addressed by removing sensitive data
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28859 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Mar 25, 2026 |
| CVE-2026-28822 |
A type confusion issue was addressed with improved memory handling
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-28863 |
A permissions issue was addressed with additional restrictions
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28879 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28856 |
The issue was addressed with improved authentication
|
4.6
Medium
|
Mar 25, 2026 |
| CVE-2026-20637 |
A use after free issue was addressed with improved memory management
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-28877 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-20698 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28882 |
This issue was addressed with improved checks
|
4.0
Medium
|
Mar 25, 2026 |
| CVE-2026-28870 |
An information leakage was addressed with additional validation
|
5.5
Medium
|
Mar 25, 2026 |
| CVE-2026-28867 |
This issue was addressed with improved authentication
|
6.2
Medium
|
Mar 25, 2026 |
| CVE-2026-20609 |
The issue was addressed with improved memory handling
|
4.4
Medium
|
Feb 11, 2026 |
| CVE-2026-20649 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20700 |
Exploited
Apple Multiple Buffer Overflow Vulnerability
|
7.8
High
|
Feb 11, 2026 |
| CVE-2026-20628 |
A permissions issue was addressed with additional restrictions
|
7.1
High
|
Feb 11, 2026 |
| CVE-2026-20635 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Feb 11, 2026 |
| CVE-2025-46301 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20654 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2025-46290 |
A logic issue was addressed with improved checks
|
7.5
High
|
Feb 11, 2026 |
| CVE-2025-46300 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20634 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20675 |
The issue was addressed with improved bounds checks
|
7.8
High
|
Feb 11, 2026 |