| CVE-2025-43443 |
This issue was addressed with improved checks
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43455 |
A privacy issue was addressed with improved checks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43394 |
This issue was addressed with improved handling of symlinks
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43434 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43361 |
An out-of-bounds read was addressed with improved bounds checking
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43336 |
A permissions issue was addressed with additional restrictions
|
4.4
Medium
|
Nov 4, 2025 |
| CVE-2025-43377 |
An out-of-bounds read was addressed with improved bounds checking
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43398 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43376 |
A logic issue was addressed with improved state management
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43399 |
This issue was addressed with improved redaction of sensitive information
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43458 |
This issue was addressed through improved state management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43419 |
The issue was addressed with improved memory handling
|
8.8
High
|
Nov 4, 2025 |
| CVE-2025-43462 |
The issue was addressed with improved memory handling
|
7.5
High
|
Nov 4, 2025 |
| CVE-2025-43435 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43423 |
A logging issue was addressed with improved data redaction
|
2.0
Low
|
Nov 4, 2025 |
| CVE-2025-43474 |
An out-of-bounds read was addressed with improved input validation
|
7.8
High
|
Nov 4, 2025 |
| CVE-2025-43395 |
This issue was addressed with improved handling of symlinks
|
3.3
Low
|
Nov 4, 2025 |
| CVE-2025-43507 |
A privacy issue was addressed by moving sensitive data
|
6.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43383 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43481 |
This issue was addressed with improved checks
|
5.2
Medium
|
Nov 4, 2025 |
| CVE-2025-43478 |
A use after free issue was addressed with improved memory management
|
5.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43424 |
The issue was addressed with improved bounds checks
|
6.5
Medium
|
Nov 4, 2025 |
| CVE-2025-43432 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Nov 4, 2025 |
| CVE-2025-43408 |
This issue was addressed by restricting options offered on a locked device
|
2.4
Low
|
Nov 4, 2025 |
| CVE-2025-43469 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Nov 4, 2025 |