| CVE-2025-43343 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43355 |
A type confusion issue was addressed with improved memory handling
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43302 |
An out-of-bounds write issue was addressed with improved bounds checking
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43359 |
A logic issue was addressed with improved state management
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43303 |
A logging issue was addressed with improved data redaction
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43354 |
A logging issue was addressed with improved data redaction
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43342 |
A correctness issue was addressed with improved checks
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43272 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43317 |
A permissions issue was addressed with additional restrictions
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43356 |
The issue was addressed with improved handling of caches
|
6.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-31255 |
An authorization issue was addressed with improved state management
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43347 |
This issue was addressed by removing the vulnerable code
|
9.8
Critique
|
15 sept. 2025 |
| CVE-2025-43346 |
An out-of-bounds access issue was addressed with improved bounds checking
|
5.5
Moyenne
|
15 sept. 2025 |
| CVE-2025-43265 |
An out-of-bounds read was addressed with improved input validation
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43216 |
A use-after-free issue was addressed with improved memory management
|
6.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-43186 |
The issue was addressed with improved memory handling
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43230 |
The issue was addressed with additional permissions checks
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-43226 |
An out-of-bounds read was addressed with improved input validation
|
4.0
Moyenne
|
29 juil. 2025 |
| CVE-2025-24224 |
The issue was addressed with improved checks
|
7.5
Élevée
|
29 juil. 2025 |
| CVE-2025-43227 |
This issue was addressed through improved state management
|
7.5
Élevée
|
29 juil. 2025 |
| CVE-2025-43211 |
The issue was addressed with improved memory handling
|
6.2
Moyenne
|
29 juil. 2025 |
| CVE-2025-43212 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
29 juil. 2025 |
| CVE-2025-43209 |
An out-of-bounds access issue was addressed with improved bounds checking
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43234 |
Multiple memory corruption issues were addressed with improved input validation
|
9.8
Critique
|
29 juil. 2025 |
| CVE-2025-43214 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
29 juil. 2025 |