| CVE-2025-31232 |
A logic issue was addressed with improved checks
|
7.1
High
|
May 12, 2025 |
| CVE-2025-31224 |
A logic issue was addressed with improved checks
|
7.8
High
|
May 12, 2025 |
| CVE-2025-31233 |
The issue was addressed with improved input sanitization
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-31209 |
An out-of-bounds read was addressed with improved bounds checking
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-31244 |
A file quarantine bypass was addressed with additional checks
|
8.8
High
|
May 12, 2025 |
| CVE-2025-31213 |
A logging issue was addressed with improved data redaction
|
7.6
High
|
May 12, 2025 |
| CVE-2025-24142 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31205 |
The issue was addressed with improved checks
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31259 |
A privacy issue was addressed with improved checks
|
7.8
High
|
May 12, 2025 |
| CVE-2025-30448 |
This issue was addressed with additional entitlement checks
|
9.1
Critical
|
May 12, 2025 |
| CVE-2025-31234 |
The issue was addressed with improved input sanitization
|
8.2
High
|
May 12, 2025 |
| CVE-2025-31218 |
This issue was addressed by removing the vulnerable code
|
6.2
Medium
|
May 12, 2025 |
| CVE-2025-31222 |
A correctness issue was addressed with improved checks
|
7.8
High
|
May 12, 2025 |
| CVE-2025-31238 |
The issue was addressed with improved checks
|
7.3
High
|
May 12, 2025 |
| CVE-2025-31242 |
A privacy issue was addressed with improved private data redaction for log entries
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31239 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
May 12, 2025 |
| CVE-2025-30453 |
The issue was addressed with additional permissions checks
|
7.8
High
|
May 12, 2025 |
| CVE-2025-31215 |
The issue was addressed with improved checks
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24144 |
An information disclosure issue was addressed by removing the vulnerable code
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31223 |
The issue was addressed with improved checks
|
8.0
High
|
May 12, 2025 |
| CVE-2025-31235 |
A double free issue was addressed with improved memory management
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31219 |
The issue was addressed with improved memory handling
|
7.1
High
|
May 12, 2025 |
| CVE-2025-31258 |
This issue was addressed by removing the vulnerable code
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24252 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Apr 29, 2025 |
| CVE-2025-31197 |
The issue was addressed with improved checks
|
5.7
Medium
|
Apr 29, 2025 |