| CVE-2025-43536 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Dec 17, 2025 |
| CVE-2025-43541 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
Dec 17, 2025 |
| CVE-2025-43501 |
A buffer overflow issue was addressed with improved memory handling
|
4.3
Medium
|
Dec 17, 2025 |
| CVE-2025-46282 |
The issue was addressed with additional permissions checks
|
5.5
Medium
|
Dec 17, 2025 |
| CVE-2025-43511 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Dec 12, 2025 |
| CVE-2025-31266 |
A spoofing issue was addressed with improved truncation when displaying the fully qualified domain name
|
4.3
Medium
|
Nov 21, 2025 |
| CVE-2023-43000 |
Exploited
Apple Multiple products Use-After-Free Vulnerability
|
8.8
High
|
Nov 5, 2025 |
| CVE-2025-43430 |
This issue was addressed through improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43502 |
A privacy issue was addressed by removing sensitive data
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43493 |
The issue was addressed with improved checks
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43503 |
An inconsistent user interface issue was addressed with improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43427 |
This issue was addressed through improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43431 |
The issue was addressed with improved memory handling
|
8.8
High
|
Nov 4, 2025 |
| CVE-2025-43457 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43441 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43421 |
Multiple issues were addressed by disabling array allocation sinking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43440 |
This issue was addressed with improved checks
|
6.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43438 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43480 |
The issue was addressed with improved checks
|
8.1
High
|
Nov 4, 2025 |
| CVE-2025-43443 |
This issue was addressed with improved checks
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43434 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43376 |
A logic issue was addressed with improved state management
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43458 |
This issue was addressed through improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43419 |
The issue was addressed with improved memory handling
|
8.8
High
|
Nov 4, 2025 |
| CVE-2025-43435 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |