| CVE-2025-43250 |
A path handling issue was addressed with improved validation
|
4.0
Medium
|
Jul 29, 2025 |
| CVE-2025-43245 |
A downgrade issue was addressed with additional code-signing restrictions
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43212 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jul 29, 2025 |
| CVE-2025-43253 |
This issue was addressed with improved input validation
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43195 |
An issue existed in the handling of environment variables
|
5.5
Medium
|
Jul 29, 2025 |
| CVE-2025-43249 |
A logic issue was addressed with improved checks
|
7.8
High
|
Jul 29, 2025 |
| CVE-2025-43199 |
A permissions issue was addressed by removing the vulnerable code
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43224 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.1
High
|
Jul 29, 2025 |
| CVE-2025-43232 |
A permissions issue was addressed with additional restrictions
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43198 |
This issue was addressed by removing the vulnerable code
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43209 |
An out-of-bounds access issue was addressed with improved bounds checking
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-24119 |
This issue was addressed through improved state management
|
7.8
High
|
Jul 29, 2025 |
| CVE-2025-43194 |
The issue was addressed with improved checks
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43252 |
This issue was addressed by adding an additional prompt for user consent
|
6.5
Medium
|
Jul 29, 2025 |
| CVE-2025-43244 |
A race condition was addressed with improved state handling
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43259 |
This issue was addressed with improved redaction of sensitive information
|
4.6
Medium
|
Jul 29, 2025 |
| CVE-2025-43275 |
A race condition was addressed with additional validation
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43234 |
Multiple memory corruption issues were addressed with improved input validation
|
9.8
Critical
|
Jul 29, 2025 |
| CVE-2025-43185 |
A downgrade issue was addressed with additional code-signing restrictions
|
5.5
Medium
|
Jul 29, 2025 |
| CVE-2025-43214 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jul 29, 2025 |
| CVE-2025-31243 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Jul 29, 2025 |
| CVE-2025-31280 |
A memory corruption issue was addressed with improved validation
|
7.8
High
|
Jul 29, 2025 |
| CVE-2025-31278 |
The issue was addressed with improved memory handling
|
8.8
High
|
Jul 29, 2025 |
| CVE-2025-43215 |
The issue was addressed with improved checks
|
5.5
Medium
|
Jul 29, 2025 |
| CVE-2025-43188 |
A permissions issue was addressed with additional restrictions
|
7.8
High
|
Jul 29, 2025 |