| CVE-2026-43703 |
The issue was addressed with improved memory handling
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-43715 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
Jun 29, 2026 |
| CVE-2026-43742 |
A use-after-free issue was addressed with improved memory management
|
6.5
Medium
|
Jun 29, 2026 |
| CVE-2026-28995 |
A logic issue was addressed with improved restrictions
|
8.8
High
|
May 11, 2026 |
| CVE-2026-28983 |
A type confusion issue was addressed with improved checks
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28940 |
The issue was addressed with improved memory handling
|
8.8
High
|
May 11, 2026 |
| CVE-2026-28917 |
The issue was addressed with improved input validation
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-39869 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28901 |
The issue was addressed with improved memory handling
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28956 |
A memory corruption issue was addressed with improved input validation
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28957 |
An issue with app access to camera metadata was addressed with improved logic
|
3.3
Low
|
May 11, 2026 |
| CVE-2026-43668 |
A use after free issue was addressed with improved memory management
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28936 |
The issue was addressed with improved checks
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28977 |
The issue was addressed with improved bounds checks
|
6.2
Medium
|
May 11, 2026 |
| CVE-2026-28920 |
An information leakage was addressed with additional validation
|
6.5
Medium
|
May 11, 2026 |
| CVE-2026-28993 |
This issue was addressed by adding an additional prompt for user consent
|
5.5
Medium
|
May 11, 2026 |
| CVE-2026-43659 |
A race condition was addressed with additional validation
|
4.7
Medium
|
May 11, 2026 |
| CVE-2026-28897 |
A buffer overflow was addressed with improved input validation
|
6.2
Medium
|
May 11, 2026 |
| CVE-2026-28907 |
The issue was addressed with improved input validation
|
8.1
High
|
May 11, 2026 |
| CVE-2026-43654 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28988 |
A permissions issue was addressed with additional restrictions
|
5.5
Medium
|
May 11, 2026 |
| CVE-2026-28971 |
The issue was addressed with improved UI handling
|
4.3
Medium
|
May 11, 2026 |
| CVE-2026-28906 |
This issue was addressed through improved state management
|
7.5
High
|
May 11, 2026 |
| CVE-2026-28947 |
A use-after-free issue was addressed with improved memory management
|
8.8
High
|
May 11, 2026 |
| CVE-2026-43658 |
The issue was addressed with improved memory handling
|
7.5
High
|
May 11, 2026 |