| CVE-2026-20621 |
The issue was addressed with improved memory handling
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20676 |
This issue was addressed through improved state management
|
4.3
Medium
|
Feb 11, 2026 |
| CVE-2026-20601 |
A permissions issue was addressed with additional restrictions
|
3.3
Low
|
Feb 11, 2026 |
| CVE-2026-20656 |
A logic issue was addressed with improved validation
|
3.3
Low
|
Feb 11, 2026 |
| CVE-2026-20617 |
A race condition was addressed with improved state handling
|
7.0
High
|
Feb 11, 2026 |
| CVE-2026-20616 |
An out-of-bounds write issue was addressed with improved bounds checking
|
8.8
High
|
Feb 11, 2026 |
| CVE-2026-20641 |
A privacy issue was addressed with improved checks
|
7.1
High
|
Feb 11, 2026 |
| CVE-2026-20677 |
A race condition was addressed with improved handling of symbolic links
|
9.0
Critical
|
Feb 11, 2026 |
| CVE-2025-43403 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20620 |
An out-of-bounds read issue was addressed with improved input validation
|
7.7
High
|
Feb 11, 2026 |
| CVE-2026-20636 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Feb 11, 2026 |
| CVE-2025-46302 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20650 |
A denial-of-service issue was addressed with improved validation
|
7.5
High
|
Feb 11, 2026 |
| CVE-2026-20646 |
A logging issue was addressed with improved data redaction
|
3.3
Low
|
Feb 11, 2026 |
| CVE-2026-20611 |
An out-of-bounds access issue was addressed with improved bounds checking
|
7.8
High
|
Feb 11, 2026 |
| CVE-2025-46305 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20666 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20627 |
An issue existed in the handling of environment variables
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2026-20671 |
A logic issue was addressed with improved checks
|
3.1
Low
|
Feb 11, 2026 |
| CVE-2026-20626 |
This issue was addressed with improved checks
|
7.8
High
|
Feb 11, 2026 |
| CVE-2026-20630 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
Feb 11, 2026 |
| CVE-2025-46304 |
The issue was addressed with improved bounds checks
|
5.7
Medium
|
Feb 11, 2026 |
| CVE-2026-20667 |
A logic issue was addressed with improved checks
|
8.8
High
|
Feb 11, 2026 |
| CVE-2026-20610 |
This issue was addressed with improved handling of symlinks
|
7.8
High
|
Feb 11, 2026 |
| CVE-2026-20647 |
This issue was addressed with improved data protection
|
5.5
Medium
|
Feb 11, 2026 |