| CVE-2026-20663 |
The issue was resolved by sanitizing logging
|
3.3
Faible
|
11 févr. 2026 |
| CVE-2025-46300 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20634 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20675 |
The issue was addressed with improved bounds checks
|
7.8
Élevée
|
11 févr. 2026 |
| CVE-2025-46303 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20660 |
A path handling issue was addressed with improved logic
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20621 |
The issue was addressed with improved memory handling
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20676 |
This issue was addressed through improved state management
|
4.3
Moyenne
|
11 févr. 2026 |
| CVE-2026-20656 |
A logic issue was addressed with improved validation
|
3.3
Faible
|
11 févr. 2026 |
| CVE-2026-20640 |
An inconsistent user interface issue was addressed with improved state management
|
4.6
Moyenne
|
11 févr. 2026 |
| CVE-2026-20617 |
A race condition was addressed with improved state handling
|
7.0
Élevée
|
11 févr. 2026 |
| CVE-2026-20616 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.8
Élevée
|
11 févr. 2026 |
| CVE-2026-20682 |
A logic issue was addressed with improved state management
|
5.3
Moyenne
|
11 févr. 2026 |
| CVE-2026-20641 |
A privacy issue was addressed with improved checks
|
7.1
Élevée
|
11 févr. 2026 |
| CVE-2026-20677 |
A race condition was addressed with improved handling of symbolic links
|
9.0
Critique
|
11 févr. 2026 |
| CVE-2026-20636 |
The issue was addressed with improved memory handling
|
6.5
Moyenne
|
11 févr. 2026 |
| CVE-2025-46302 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20661 |
An authorization issue was addressed with improved state management
|
4.6
Moyenne
|
11 févr. 2026 |
| CVE-2026-20650 |
A denial-of-service issue was addressed with improved validation
|
7.5
Élevée
|
11 févr. 2026 |
| CVE-2026-20611 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
Élevée
|
11 févr. 2026 |
| CVE-2025-46305 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |
| CVE-2026-20627 |
An issue existed in the handling of environment variables
|
5.5
Moyenne
|
11 févr. 2026 |
| CVE-2026-20671 |
A logic issue was addressed with improved checks
|
3.1
Faible
|
11 févr. 2026 |
| CVE-2026-20626 |
This issue was addressed with improved checks
|
7.8
Élevée
|
11 févr. 2026 |
| CVE-2025-46304 |
The issue was addressed with improved bounds checks
|
5.7
Moyenne
|
11 févr. 2026 |