| 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-31210 |
The issue was addressed with improved UI
|
6.5
Medium
|
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-24225 |
An injection issue was addressed with improved input validation
|
6.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-31245 |
The issue was addressed with improved checks
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31228 |
The issue was addressed with improved authentication
|
6.8
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-31213 |
A logging issue was addressed with improved data redaction
|
7.6
High
|
May 12, 2025 |
| CVE-2025-30448 |
This issue was addressed with additional entitlement checks
|
9.1
Critical
|
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-31235 |
A double free issue was addressed with improved memory management
|
6.5
Medium
|
May 12, 2025 |
| CVE-2025-24220 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
May 12, 2025 |
| CVE-2025-31219 |
The issue was addressed with improved memory handling
|
7.1
High
|
May 12, 2025 |
| CVE-2025-24091 |
An app could impersonate system notifications
|
5.5
Medium
|
Apr 30, 2025 |
| CVE-2025-24252 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Apr 29, 2025 |