| CVE-2025-43384 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43500 |
A privacy issue was addressed with improved handling of user preferences
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43445 |
An out-of-bounds read was addressed with improved input validation
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43392 |
The issue was addressed with improved handling of caches
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43444 |
A permissions issue was addressed with additional restrictions
|
5.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43413 |
An access issue was addressed with additional sandbox restrictions
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43385 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43429 |
A buffer overflow was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43448 |
This issue was addressed with improved validation of symlinks
|
6.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43389 |
A privacy issue was addressed by removing the vulnerable code
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43433 |
The issue was addressed with improved memory handling
|
8.8
High
|
Nov 4, 2025 |
| CVE-2025-43425 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43282 |
A double free issue was addressed with improved memory management
|
5.5
Medium
|
Oct 15, 2025 |
| CVE-2025-43400 |
An out-of-bounds write issue was addressed with improved bounds checking
|
6.3
Medium
|
Sep 29, 2025 |
| CVE-2025-43349 |
An out-of-bounds write issue was addressed with improved input validation
|
2.8
Low
|
Sep 15, 2025 |
| CVE-2025-43344 |
An out-of-bounds access issue was addressed with improved bounds checking
|
3.3
Low
|
Sep 15, 2025 |
| CVE-2025-43190 |
A parsing issue in the handling of directory paths was addressed with improved path validation
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43372 |
The issue was addressed with improved input validation
|
6.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43343 |
The issue was addressed with improved memory handling
|
9.8
Critical
|
Sep 15, 2025 |
| CVE-2025-43355 |
A type confusion issue was addressed with improved memory handling
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43302 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43359 |
A logic issue was addressed with improved state management
|
9.8
Critical
|
Sep 15, 2025 |
| CVE-2025-43303 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43354 |
A logging issue was addressed with improved data redaction
|
5.5
Medium
|
Sep 15, 2025 |
| CVE-2025-43342 |
A correctness issue was addressed with improved checks
|
9.8
Critical
|
Sep 15, 2025 |