This page was not yet optimized for use on mobile devices.
Samsung Android 16.0 SMR-JAN-2026-R1
Configuration details
| CPE title | Samsung Android 16.0 SMR-JAN-2026-R1 |
|---|---|
| URI | cpe:2.3:o:samsung:android:16.0:smr-jan-2026-r1:*:*:*:*:*:* |
Linked CVEs
67 CVEs| ID | Links | Severity | CVSS Score | Published on |
|---|---|---|---|---|
| Base score | ||||
| CVE-2026-20977 | MEDIUM | 5.5 | 04.02.2026 | |
| CVE-2026-20978 | MEDIUM | 6.1 | 04.02.2026 | |
| CVE-2026-20979 | HIGH | 7.8 | 04.02.2026 | |
| CVE-2026-20980 | MEDIUM | 6.8 | 04.02.2026 | |
| CVE-2026-20981 | MEDIUM | 6.6 | 04.02.2026 | |
| CVE-2026-20982 | MEDIUM | 6.0 | 04.02.2026 | |
| CVE-2026-20988 | MEDIUM | 5.0 | 16.03.2026 | |
| CVE-2026-20989 | LOW | 2.4 | 16.03.2026 | |
| CVE-2026-20990 | HIGH | 8.1 | 16.03.2026 | |
| CVE-2026-20991 | MEDIUM | 4.4 | 16.03.2026 | |
| CVE-2026-20992 | LOW | 3.3 | 16.03.2026 | |
| CVE-2026-21003 | MEDIUM | 6.8 | 13.04.2026 | |
| CVE-2026-21007 | MEDIUM | 6.8 | 13.04.2026 | |
| CVE-2026-21008 | MEDIUM | 6.5 | 13.04.2026 | |
| CVE-2026-21009 | MEDIUM | 6.8 | 13.04.2026 | |
| CVE-2026-21010 | HIGH | 7.8 | 13.04.2026 | |
| CVE-2026-21011 | MEDIUM | 6.8 | 13.04.2026 | |
| CVE-2026-21012 | LOW | 3.3 | 13.04.2026 | |
| CVE-2026-21015 | MEDIUM | 5.5 | 13.05.2026 | |
| CVE-2026-21016 | MEDIUM | 5.5 | 13.05.2026 | |
| CVE-2026-21017 | MEDIUM | 5.5 | 05.06.2026 | |
| CVE-2026-21018 | MEDIUM | 6.7 | 13.05.2026 | |
| CVE-2026-21020 | HIGH | 7.8 | 13.05.2026 | |
| CVE-2026-21021 | MEDIUM | 6.8 | 13.05.2026 | |
| CVE-2026-21022 | MEDIUM | 5.5 | 13.05.2026 | |
| CVE-2026-21023 | MEDIUM | 5.5 | 29.04.2026 | |
| CVE-2026-21025 | MEDIUM | 5.5 | 05.06.2026 | |
| CVE-2026-21026 | MEDIUM | 5.5 | 05.06.2026 | |
| CVE-2026-21027 | LOW | 3.3 | 05.06.2026 | |
| CVE-2026-21028 | MEDIUM | 5.5 | 05.06.2026 | |
| CVE-2026-21029 | HIGH | 7.8 | 05.06.2026 | |
| CVE-2026-21030 | HIGH | 7.8 | 05.06.2026 | |
| CVE-2026-21031 | HIGH | 7.8 | 05.06.2026 | |
| CVE-2026-21058 | HIGH | 7.1 | 10.08.2026 | |
| CVE-2026-21059 | HIGH | 7.1 | 10.08.2026 | |
| CVE-2026-21060 | MEDIUM | 4.6 | 10.08.2026 | |
| CVE-2026-21061 | MEDIUM | 6.5 | 10.08.2026 | |
| CVE-2026-21062 | LOW | 3.3 | 10.08.2026 | |
| CVE-2026-21063 | MEDIUM | 6.1 | 10.08.2026 | |
| CVE-2026-21064 | MEDIUM | 5.5 | 10.08.2026 | |
| CVE-2026-21065 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21066 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21067 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21068 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21069 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21071 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21072 | HIGH | 7.8 | 10.08.2026 | |
| CVE-2026-21073 | MEDIUM | 6.1 | 10.08.2026 | |
| CVE-2026-21085 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21087 | HIGH | 7.8 | 09.09.2026 | |
| CVE-2026-21088 | HIGH | 7.8 | 09.09.2026 | |
| CVE-2026-21089 | HIGH | 7.8 | 09.09.2026 | |
| CVE-2026-21090 | HIGH | 7.8 | 09.09.2026 | |
| CVE-2026-21091 | HIGH | 7.8 | 09.09.2026 | |
| CVE-2026-21092 | MEDIUM | 5.3 | 09.09.2026 | |
| CVE-2026-21093 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21094 | HIGH | 8.8 | 09.09.2026 | |
| CVE-2026-21095 | CRITICAL | 9.8 | 09.09.2026 | |
| CVE-2026-21096 | CRITICAL | 9.8 | 09.09.2026 | |
| CVE-2026-21097 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21099 | MEDIUM | 5.5 | 09.09.2026 | |
| CVE-2026-21100 | HIGH | 7.1 | 09.09.2026 | |
| CVE-2026-21101 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21102 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21103 | MEDIUM | 6.1 | 09.09.2026 | |
| CVE-2026-21104 | MEDIUM | 6.7 | 09.09.2026 | |
| CVE-2026-21112 | MEDIUM | 5.5 | 09.09.2026 |
Showing 5 out of 67.