| CVE-2025-46282 |
The issue was addressed with additional permissions checks
|
5.5
Medium
|
Dec 17, 2025 |
| CVE-2025-46277 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Dec 17, 2025 |
| CVE-2025-43518 |
A logic issue was addressed with improved checks
|
3.3
Low
|
Dec 12, 2025 |
| CVE-2025-43522 |
A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions
|
3.3
Low
|
Dec 12, 2025 |
| CVE-2025-43467 |
This issue was addressed with improved checks
|
7.8
High
|
Dec 12, 2025 |
| CVE-2025-43471 |
The issue was addressed with improved checks
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43406 |
A logic issue was addressed with improved restrictions
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43410 |
The issue was addressed with improved handling of caches
|
2.4
Low
|
Dec 12, 2025 |
| CVE-2025-43538 |
A logging issue was addressed with improved data redaction
|
3.3
Low
|
Dec 12, 2025 |
| CVE-2025-43539 |
The issue was addressed with improved bounds checks
|
8.8
High
|
Dec 12, 2025 |
| CVE-2025-43542 |
This issue was addressed with improved state management
|
7.5
High
|
Dec 12, 2025 |
| CVE-2025-43470 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43523 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43466 |
An injection issue was addressed with improved validation
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43519 |
A permissions issue was addressed with additional restrictions
|
7.5
High
|
Dec 12, 2025 |
| CVE-2025-43512 |
A logic issue was addressed with improved checks
|
7.8
High
|
Dec 12, 2025 |
| CVE-2025-43416 |
A logic issue was addressed with improved restrictions
|
9.8
Critical
|
Dec 12, 2025 |
| CVE-2025-43482 |
The issue was addressed with improved input validation
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-46287 |
An inconsistent user interface issue was addressed with improved state management
|
9.8
Critical
|
Dec 12, 2025 |
| CVE-2025-43494 |
A mail header parsing issue was addressed with improved checks
|
7.5
High
|
Dec 12, 2025 |
| CVE-2025-43461 |
This issue was addressed with improved validation of symlinks
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43532 |
A memory corruption issue was addressed with improved bounds checking
|
2.8
Low
|
Dec 12, 2025 |
| CVE-2025-43509 |
This issue was addressed with improved data protection
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43381 |
This issue was addressed with improved handling of symlinks
|
5.5
Medium
|
Dec 12, 2025 |
| CVE-2025-43513 |
A permissions issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Dec 12, 2025 |