| CVE-2025-43291 |
A permissions issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-24197 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43317 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43340 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Sep 15, 2025 |
| CVE-2025-43356 |
The issue was addressed with improved handling of caches
|
6.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43301 |
A privacy issue was addressed with improved private data redaction for log entries
|
3.3
Low
|
Sep 15, 2025 |
| CVE-2025-43367 |
A privacy issue was addressed by moving sensitive data
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43330 |
This issue was addressed by removing the vulnerable code
|
8.2
High
|
Sep 15, 2025 |
| CVE-2025-43326 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-31255 |
An authorization issue was addressed with improved state management
|
9.8
Critical
|
Sep 15, 2025 |
| CVE-2025-43347 |
This issue was addressed by removing the vulnerable code
|
9.8
Critical
|
Sep 15, 2025 |
| CVE-2025-43310 |
A configuration issue was addressed with additional restrictions
|
4.4
Medium
|
Sep 15, 2025 |
| CVE-2025-43279 |
A privacy issue was addressed with improved private data redaction for log entries
|
6.2
Medium
|
Sep 15, 2025 |
| CVE-2025-43297 |
A type confusion issue was addressed with improved memory handling
|
6.2
Medium
|
Sep 15, 2025 |
| CVE-2025-43311 |
This issue was addressed with additional entitlement checks
|
5.1
Medium
|
Sep 15, 2025 |
| CVE-2025-43346 |
An out-of-bounds access issue was addressed with improved bounds checking
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43307 |
This issue was addressed with improved checks to prevent unauthorized actions
|
4.0
Medium
|
Sep 15, 2025 |
| CVE-2025-43327 |
The issue was addressed by adding additional logic
|
6.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43262 |
A permissions issue was addressed with additional restrictions
|
5.1
Medium
|
Sep 15, 2025 |
| CVE-2025-43331 |
A downgrade issue was addressed with additional code-signing restrictions
|
4.0
Medium
|
Sep 15, 2025 |
| CVE-2025-43366 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2024-54554 |
This issue was addressed with improved handling of symlinks
|
5.5
Medium
|
Aug 29, 2025 |
| CVE-2025-43187 |
This issue was addressed by removing the vulnerable code
|
7.8
High
|
Aug 29, 2025 |
| CVE-2025-43284 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Aug 29, 2025 |
| CVE-2024-54568 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Aug 29, 2025 |