| CVE-2025-43384 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43500 |
A privacy issue was addressed with improved handling of user preferences
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43412 |
A file quarantine bypass was addressed with additional checks
|
6.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43445 |
An out-of-bounds read was addressed with improved input validation
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43392 |
The issue was addressed with improved handling of caches
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43405 |
A permissions issue was addressed with additional sandbox restrictions
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43444 |
A permissions issue was addressed with additional restrictions
|
5.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43413 |
An access issue was addressed with additional sandbox restrictions
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43385 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43468 |
A downgrade issue affecting Intel-based Mac computers was addressed with additional code-signing restrictions
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43429 |
A buffer overflow was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43409 |
A permissions issue was addressed with additional sandbox restrictions
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43448 |
This issue was addressed with improved validation of symlinks
|
6.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43389 |
A privacy issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43433 |
The issue was addressed with improved memory handling
|
8.8
High
|
Nov 4, 2025 |
| CVE-2025-43425 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43472 |
A validation issue was addressed with improved input sanitization
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43282 |
A double free issue was addressed with improved memory management
|
5.5
Medium
|
Oct 15, 2025 |
| CVE-2025-43313 |
A logic issue was addressed with improved restrictions
|
5.5
Medium
|
Oct 15, 2025 |
| CVE-2025-43281 |
The issue was addressed with improved authentication
|
7.8
High
|
Oct 15, 2025 |
| CVE-2025-43296 |
A logic issue was addressed with improved validation
|
5.5
Medium
|
Oct 9, 2025 |
| CVE-2025-43400 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.3
Medium
|
Sep 29, 2025 |
| CVE-2025-43332 |
A file quarantine bypass was addressed with additional checks
|
5.2
Medium
|
Sep 15, 2025 |
| CVE-2025-43298 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
7.8
High
|
Sep 15, 2025 |
| CVE-2025-43349 |
An out-of-bounds write issue was addressed with improved input validation
|
2.8
Low
|
Sep 15, 2025 |