| CVE-2025-31257 |
This issue was addressed with improved memory handling
|
4.7
Medium
|
May 12, 2025 |
| CVE-2025-31217 |
The issue was addressed with improved input validation
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24111 |
A memory corruption issue was addressed with improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31221 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31206 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
May 12, 2025 |
| CVE-2025-31251 |
The issue was addressed with improved input sanitization
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31226 |
A logic issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31196 |
An out-of-bounds read was addressed with improved input validation
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31204 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 12, 2025 |
| CVE-2025-31212 |
This issue was addressed through improved state management
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31245 |
The issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31208 |
The issue was addressed with improved checks
|
7.5
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-31205 |
The issue was addressed with improved checks
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31234 |
The issue was addressed with improved input sanitization
|
8.2
High
|
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-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-31219 |
The issue was addressed with improved memory handling
|
7.1
High
|
May 12, 2025 |
| CVE-2025-24252 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Apr 29, 2025 |