| CVE-2025-31257 |
This issue was addressed with improved memory handling
|
4.7
Medium
|
May 12, 2025 |
| CVE-2025-31256 |
The issue was addressed with improved handling of caches
|
5.5
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-31240 |
This issue was addressed with improved checks
|
7.5
High
|
May 12, 2025 |
| CVE-2025-24222 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-31237 |
This issue was addressed with improved checks
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31221 |
An integer overflow was addressed with improved input validation
|
7.5
High
|
May 12, 2025 |
| CVE-2025-31260 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31247 |
A logic issue was addressed with improved state management
|
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-30440 |
The issue was addressed with improved checks
|
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-31250 |
An information disclosure issue was addressed with improved privacy controls
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31246 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 12, 2025 |
| CVE-2025-31195 |
The issue was addressed by adding additional logic
|
6.3
Medium
|
May 12, 2025 |
| CVE-2025-30442 |
The issue was addressed with improved input sanitization
|
7.8
High
|
May 12, 2025 |
| CVE-2025-31204 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 12, 2025 |
| CVE-2025-24155 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
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-31249 |
A logic issue was addressed with improved checks
|
7.1
High
|
May 12, 2025 |