| CVE-2025-24235 |
A memory initialization issue was addressed with improved memory handling
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24242 |
This issue was addressed with improved handling of symlinks
|
4.4
Medium
|
Mar 31, 2025 |
| CVE-2025-24215 |
The issue was addressed with improved checks
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24203 |
The issue was addressed with improved checks
|
5.0
Medium
|
Mar 31, 2025 |
| CVE-2025-24192 |
A script imports issue was addressed with improved isolation
|
6.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24254 |
This issue was addressed with improved validation of symlinks
|
8.8
High
|
Mar 31, 2025 |
| CVE-2025-30450 |
This issue was addressed with improved validation of symlinks
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-31187 |
This issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24278 |
This issue was addressed with improved validation of symlinks
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-30446 |
A permissions issue was addressed with additional restrictions
|
6.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24281 |
This issue was addressed with improved data protection
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24239 |
A downgrade issue was addressed with additional code-signing restrictions
|
6.5
Medium
|
Mar 31, 2025 |
| CVE-2025-31191 |
This issue was addressed through improved state management
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24238 |
A logic issue was addressed with improved checks
|
9.8
Critical
|
Mar 31, 2025 |
| CVE-2025-30447 |
The issue was resolved by sanitizing logging
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24280 |
An access issue was addressed with additional sandbox restrictions
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24279 |
This issue was addressed with improved file handling
|
4.3
Medium
|
Mar 31, 2025 |
| CVE-2025-30451 |
This issue was addressed with improved redaction of sensitive information
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24255 |
A file access issue was addressed with improved input validation
|
8.4
High
|
Mar 31, 2025 |
| CVE-2025-24202 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24214 |
A privacy issue was addressed by not logging contents of text fields
|
5.5
Medium
|
Mar 31, 2025 |
| CVE-2025-24097 |
A permissions issue was addressed with additional restrictions
|
5.0
Medium
|
Mar 31, 2025 |
| CVE-2025-24243 |
The issue was addressed with improved memory handling
|
7.8
High
|
Mar 31, 2025 |
| CVE-2025-24234 |
This issue was addressed by removing the vulnerable code
|
7.8
High
|
Mar 31, 2025 |
| CVE-2025-24263 |
A privacy issue was addressed by moving sensitive data to a protected location
|
9.8
Critical
|
Mar 31, 2025 |