| CVE-2025-31248 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
5.5
Medium
|
Nov 21, 2025 |
| CVE-2025-43205 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.0
Medium
|
Nov 12, 2025 |
| CVE-2023-43000 |
Exploited
Apple Multiple products Use-After-Free Vulnerability
|
8.8
High
|
Nov 5, 2025 |
| CVE-2025-43373 |
The issue was addressed with improved memory handling
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43430 |
This issue was addressed through improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43426 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43390 |
A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43447 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43502 |
A privacy issue was addressed by removing sensitive data
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43386 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43345 |
A correctness issue was addressed with improved checks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43493 |
The issue was addressed with improved checks
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43387 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43411 |
This issue was addressed with additional entitlement checks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43446 |
This issue was addressed with improved validation of symlinks
|
5.5
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-43391 |
A privacy issue was addressed with improved handling of temporary files
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43407 |
This issue was addressed with improved entitlements
|
7.8
High
|
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-43348 |
A logic issue was addressed with improved validation
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43364 |
A race condition was addressed with additional validation
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43396 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43379 |
This issue was addressed with improved validation of symlinks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43457 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Nov 4, 2025 |