| CVE-2026-65353 |
An authorization issue was addressed with improved state management
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84624 |
A permissions issue was addressed with improved path validation
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-65365 |
An out-of-bounds read was addressed with improved bounds checking
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-28934 |
A buffer overflow was addressed with improved bounds checking
|
6.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84632 |
The issue was addressed with improved memory handling
|
7.3
High
|
Sep 14, 2026 |
| CVE-2026-84560 |
An authorization issue was addressed with improved state management
|
6.1
Medium
|
Sep 14, 2026 |
| CVE-2026-84521 |
A use after free issue was addressed with improved memory management
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-84537 |
The issue was addressed with improved memory handling
|
6.6
Medium
|
Sep 14, 2026 |
| CVE-2026-84576 |
This issue was addressed with improved checks
|
5.5
Medium
|
Sep 14, 2026 |
| CVE-2026-64705 |
A buffer overflow was addressed with improved bounds checking
|
5.5
Medium
|
Aug 25, 2026 |
| CVE-2026-43670 |
A Content Security Policy bypass was addressed with improved enforcement in AudioWorklet contexts
|
8.8
High
|
Aug 25, 2026 |
| CVE-2026-20679 |
The issue was addressed with improved checks
|
4.3
Medium
|
Aug 21, 2026 |
| CVE-2026-65331 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64760 |
An information leakage was addressed with additional validation
|
5.5
Medium
|
Aug 17, 2026 |
| CVE-2026-43794 |
A memory corruption issue was addressed with improved memory handling
|
8.8
High
|
Aug 17, 2026 |
| CVE-2026-65346 |
An integer overflow was addressed with improved input validation
|
8.8
High
|
Aug 17, 2026 |
| CVE-2026-65351 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64782 |
A memory corruption vulnerability was addressed with improved locking
|
3.1
Low
|
Aug 17, 2026 |
| CVE-2026-65347 |
The issue was addressed with improved checks
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-43795 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65330 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Aug 17, 2026 |
| CVE-2026-65340 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-65337 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |
| CVE-2026-64788 |
The issue was addressed with improved memory handling
|
5.4
Medium
|
Aug 17, 2026 |
| CVE-2026-65336 |
This issue was addressed through improved state management
|
4.3
Medium
|
Aug 17, 2026 |