| CVE-2026-20621 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20676 |
This issue was addressed through improved state management
|
4.3
Medium
|
Feb 11, 2026 |
| CVE-2026-20617 |
A race condition was addressed with improved state handling
|
7.0
High
|
Feb 11, 2026 |
| CVE-2026-20616 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.8
High
|
Feb 11, 2026 |
| CVE-2026-20641 |
A privacy issue was addressed with improved checks
|
7.1
High
|
Feb 11, 2026 |
| CVE-2026-20677 |
A race condition was addressed with improved handling of symbolic links
|
9.0
Critical
|
Feb 11, 2026 |
| CVE-2026-20636 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Feb 11, 2026 |
| CVE-2025-46302 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20650 |
A denial-of-service issue was addressed with improved validation
|
7.5
High
|
Feb 11, 2026 |
| CVE-2026-20611 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
High
|
Feb 11, 2026 |
| CVE-2025-46305 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20627 |
An issue existed in the handling of environment variables
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20671 |
A logic issue was addressed with improved checks
|
3.1
Low
|
Feb 11, 2026 |
| CVE-2026-20626 |
This issue was addressed with improved checks
|
7.8
High
|
Feb 11, 2026 |
| CVE-2025-46304 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2025-46298 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jan 9, 2026 |
| CVE-2025-46299 |
A memory initialization issue was addressed with improved memory handling
|
4.3
Medium
|
Jan 9, 2026 |
| CVE-2025-46279 |
A permissions issue was addressed with additional restrictions
|
9.8
Critical
|
Dec 17, 2025 |
| CVE-2025-43535 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Dec 17, 2025 |
| CVE-2025-43533 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Dec 17, 2025 |
| CVE-2025-43529 |
Exploited
Apple Multiple Products Use-After-Free WebKit Vulnerability
|
8.8
High
|
Dec 17, 2025 |
| CVE-2025-46288 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Dec 17, 2025 |
| CVE-2025-43531 |
A race condition was addressed with improved state handling
|
3.1
Low
|
Dec 17, 2025 |
| CVE-2025-43428 |
A configuration issue was addressed with additional restrictions
|
9.8
Critical
|
Dec 17, 2025 |
| CVE-2025-43541 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
Dec 17, 2025 |