| 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-43503 |
An inconsistent user interface issue was addressed with improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43450 |
A logic issue was addressed with improved checks
|
7.5
High
|
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-43309 |
A logic issue was addressed with improved checks
|
2.4
Low
|
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-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 |
| CVE-2025-43441 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43338 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.1
High
|
Nov 4, 2025 |
| CVE-2025-43436 |
A permissions issue was addressed with additional restrictions
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43498 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43499 |
This issue was addressed with additional entitlement checks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43421 |
Multiple issues were addressed by disabling array allocation sinking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43460 |
A logic issue was addressed with improved checks
|
4.6
Medium
|
Nov 4, 2025 |
| CVE-2025-43323 |
This issue was addressed with additional entitlement checks
|
8.1
High
|
Nov 4, 2025 |
| CVE-2025-43495 |
The issue was addressed with improved checks
|
5.4
Medium
|
Nov 4, 2025 |
| CVE-2025-43440 |
This issue was addressed with improved checks
|
6.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43496 |
The issue was addressed by adding additional logic
|
7.5
High
|
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 |