en
Severity across 100 analyzed records
A short verification protects source data and prevents automated AI requests.
The GCVE catalog currently lists 852 vulnerability records affecting Samsung Mobile Devices.
Among the 100 records analyzed by CyStack, 22 are High or Critical and 0 appear in the CISA KEV catalog.
Compare the version you run with each vulnerability and the provider guidance below. The data only includes records analyzed so far.
| CVE | Exploitation status | Fix | Published | Severity |
|---|---|---|---|---|
CVE-2026-21104CVE-2026-21104 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityHigh |
CVE-2026-21103CVE-2026-21103 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21102CVE-2026-21102 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityCritical |
CVE-2026-21101CVE-2026-21101 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityHigh |
CVE-2026-21100CVE-2026-21100 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21099CVE-2026-21099 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21098CVE-2026-21098 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21097CVE-2026-21097 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21096CVE-2026-21096 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityCritical |
CVE-2026-21095CVE-2026-21095 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityCritical |
CVE-2026-21094CVE-2026-21094 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21093CVE-2026-21093 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21092CVE-2026-21092 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityHigh |
CVE-2026-21091CVE-2026-21091 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21090CVE-2026-21090 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21089CVE-2026-21089 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21088CVE-2026-21088 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21087CVE-2026-21087 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityHigh |
CVE-2026-21086CVE-2026-21086 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityMedium |
CVE-2026-21085CVE-2026-21085 | Exploitation statusNot known exploited | FixNot confirmed | Published09/09/2026 | SeverityHigh |
CVE-2026-21073CVE-2026-21073 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21072CVE-2026-21072 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21071CVE-2026-21071 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21070CVE-2026-21070 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21069CVE-2026-21069 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21068CVE-2026-21068 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityHigh |
CVE-2026-21067CVE-2026-21067 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21066CVE-2026-21066 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21065CVE-2026-21065 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21064CVE-2026-21064 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityHigh |
CVE-2026-21063CVE-2026-21063 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21062CVE-2026-21062 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21061CVE-2026-21061 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21060CVE-2026-21060 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21059CVE-2026-21059 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21058CVE-2026-21058 | Exploitation statusNot known exploited | FixNot confirmed | Published08/10/2026 | SeverityMedium |
CVE-2026-21047CVE-2026-21047 | Exploitation statusNot known exploited | FixNot confirmed | Published07/28/2026 | SeverityHigh |
CVE-2026-21052CVE-2026-21052 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21051CVE-2026-21051 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21050CVE-2026-21050 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21049CVE-2026-21049 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityHigh |
CVE-2026-21048CVE-2026-21048 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityHigh |
CVE-2026-21046CVE-2026-21046 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityHigh |
CVE-2026-21045CVE-2026-21045 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityHigh |
CVE-2026-21044CVE-2026-21044 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21043CVE-2026-21043 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21042CVE-2026-21042 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityHigh |
CVE-2026-21041CVE-2026-21041 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21040CVE-2026-21040 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21039CVE-2026-21039 | Exploitation statusNot known exploited | FixNot confirmed | Published07/10/2026 | SeverityMedium |
CVE-2026-21031CVE-2026-21031 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21030CVE-2026-21030 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21029CVE-2026-21029 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21028CVE-2026-21028 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21027CVE-2026-21027 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21026CVE-2026-21026 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21025CVE-2026-21025 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21017CVE-2026-21017 | Exploitation statusNot known exploited | FixNot confirmed | Published06/05/2026 | SeverityMedium |
CVE-2026-21022CVE-2026-21022 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21021CVE-2026-21021 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21020CVE-2026-21020 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21019CVE-2026-21019 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityHigh |
CVE-2026-21018CVE-2026-21018 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21016CVE-2026-21016 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21015CVE-2026-21015 | Exploitation statusNot known exploited | FixNot confirmed | Published05/13/2026 | SeverityMedium |
CVE-2026-21023CVE-2026-21023 | Exploitation statusNot known exploited | FixNot confirmed | Published04/29/2026 | SeverityMedium |
CVE-2026-21010CVE-2026-21010 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21008CVE-2026-21008 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21012CVE-2026-21012 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21011CVE-2026-21011 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21009CVE-2026-21009 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21007CVE-2026-21007 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21006CVE-2026-21006 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-21003CVE-2026-21003 | Exploitation statusNot known exploited | FixNot confirmed | Published04/13/2026 | SeverityMedium |
CVE-2026-20992CVE-2026-20992 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityMedium |
CVE-2026-20991CVE-2026-20991 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityMedium |
CVE-2026-20990CVE-2026-20990 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityHigh |
CVE-2026-20989CVE-2026-20989 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityMedium |
CVE-2026-20988CVE-2026-20988 | Exploitation statusNot known exploited | FixNot confirmed | Published03/16/2026 | SeverityMedium |
CVE-2026-20983CVE-2026-20983 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityHigh |
CVE-2026-20982CVE-2026-20982 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityMedium |
CVE-2026-20981CVE-2026-20981 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityMedium |
CVE-2026-20980CVE-2026-20980 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityHigh |
CVE-2026-20979CVE-2026-20979 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityHigh |
CVE-2026-20978CVE-2026-20978 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityMedium |
CVE-2026-20977CVE-2026-20977 | Exploitation statusNot known exploited | FixNot confirmed | Published02/04/2026 | SeverityMedium |
CVE-2026-20974CVE-2026-20974 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityMedium |
CVE-2026-20973CVE-2026-20973 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityMedium |
CVE-2026-20972CVE-2026-20972 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityMedium |
CVE-2026-20971CVE-2026-20971 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityHigh |
CVE-2026-20970CVE-2026-20970 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityMedium |
CVE-2026-20969CVE-2026-20969 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityLow |
CVE-2026-20968CVE-2026-20968 | Exploitation statusNot known exploited | FixNot confirmed | Published01/09/2026 | SeverityMedium |
CVE-2025-58480CVE-2025-58480 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-58479CVE-2025-58479 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-58478CVE-2025-58478 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-58477CVE-2025-58477 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-58476CVE-2025-58476 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-58475CVE-2025-58475 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CVE-2025-21080CVE-2025-21080 | Exploitation statusNot known exploited | FixNot confirmed | Published12/02/2025 | SeverityMedium |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
