| CVE-2025-43457 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43441 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43436 |
A permissions issue was addressed with additional restrictions
|
7.5
Élevée
|
4 nov. 2025 |
| CVE-2025-43498 |
An authorization issue was addressed with improved state management
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43421 |
Multiple issues were addressed by disabling array allocation sinking
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43323 |
This issue was addressed with additional entitlement checks
|
8.1
Élevée
|
4 nov. 2025 |
| CVE-2025-43440 |
This issue was addressed with improved checks
|
6.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43496 |
The issue was addressed by adding additional logic
|
7.5
Élevée
|
4 nov. 2025 |
| CVE-2025-43438 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43480 |
The issue was addressed with improved checks
|
8.1
Élevée
|
4 nov. 2025 |
| CVE-2025-43443 |
This issue was addressed with improved checks
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43455 |
A privacy issue was addressed with improved checks
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43434 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43361 |
An out-of-bounds read was addressed with improved bounds checking
|
7.8
Élevée
|
4 nov. 2025 |
| CVE-2025-43398 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43376 |
A logic issue was addressed with improved state management
|
7.5
Élevée
|
4 nov. 2025 |
| CVE-2025-43458 |
This issue was addressed through improved state management
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43419 |
The issue was addressed with improved memory handling
|
8.8
Élevée
|
4 nov. 2025 |
| CVE-2025-43462 |
The issue was addressed with improved memory handling
|
7.5
Élevée
|
4 nov. 2025 |
| CVE-2025-43435 |
The issue was addressed with improved memory handling
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43423 |
A logging issue was addressed with improved data redaction
|
2.0
Faible
|
4 nov. 2025 |
| CVE-2025-43507 |
A privacy issue was addressed by moving sensitive data
|
6.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43383 |
An out-of-bounds access issue was addressed with improved bounds checking
|
4.3
Moyenne
|
4 nov. 2025 |
| CVE-2025-43439 |
A privacy issue was addressed by removing sensitive data
|
5.5
Moyenne
|
4 nov. 2025 |
| CVE-2025-43432 |
A use-after-free issue was addressed with improved memory management
|
4.3
Moyenne
|
4 nov. 2025 |