| CVE-2026-113904 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-113949 |
A type confusion issue was addressed with improved state management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112621 |
An out-of-bounds write issue was addressed with improved bounds checking
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112699 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112637 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-86986 |
A use-after-free issue was addressed with improved memory management
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112695 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-113952 |
A logic issue was addressed with improved checks
|
5.4
Medium
|
Oct 26, 2026 |
| CVE-2026-112640 |
A use-after-free issue was addressed with improved memory management
|
7.6
High
|
Oct 26, 2026 |
| CVE-2026-86973 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112626 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-112651 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |
| CVE-2026-86974 |
A type confusion issue was addressed with improved checks
|
7.5
High
|
Oct 26, 2026 |
| CVE-2026-112684 |
This issue was addressed through improved state management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112693 |
A use-after-free issue was addressed with improved memory management
|
Not rated
|
Oct 26, 2026 |
| CVE-2026-113903 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112666 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112673 |
A type confusion issue was addressed with improved state handling
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112599 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112686 |
A race condition was addressed with improved locking
|
3.1
Low
|
Oct 26, 2026 |
| CVE-2026-112669 |
A race condition was addressed with improved state handling
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112653 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-113901 |
A use-after-free issue was addressed with improved memory management
|
4.3
Medium
|
Oct 26, 2026 |
| CVE-2026-112680 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Oct 26, 2026 |
| CVE-2026-112655 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Oct 26, 2026 |