en
Severity across 1 analyzed records
A short verification protects source data and prevents automated AI requests.
| CVE | Exploitation status | Fix | Affected product | Published | Severity |
|---|---|---|---|---|---|
CVE-2026-21104CVE-2026-21104 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21103CVE-2026-21103 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21102CVE-2026-21102 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityCritical |
CVE-2026-21101CVE-2026-21101 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21100CVE-2026-21100 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21099CVE-2026-21099 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21097CVE-2026-21097 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21089CVE-2026-21089 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21088CVE-2026-21088 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21087CVE-2026-21087 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21085CVE-2026-21085 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21083CVE-2026-21083 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published08/10/2026 | SeverityMedium |
CVE-2026-21082CVE-2026-21082 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Health | Published08/10/2026 | SeverityMedium |
CVE-2026-21080CVE-2026-21080 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published08/10/2026 | SeverityMedium |
CVE-2026-21079CVE-2026-21079 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published08/10/2026 | SeverityHigh |
CVE-2026-21078CVE-2026-21078 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published08/10/2026 | SeverityMedium |
CVE-2026-21077CVE-2026-21077 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Health | Published08/10/2026 | SeverityMedium |
CVE-2026-21076CVE-2026-21076 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Health | Published08/10/2026 | SeverityMedium |
CVE-2026-21073CVE-2026-21073 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21072CVE-2026-21072 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21071CVE-2026-21071 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21070CVE-2026-21070 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21069CVE-2026-21069 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21068CVE-2026-21068 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityHigh |
CVE-2026-21067CVE-2026-21067 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21066CVE-2026-21066 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21065CVE-2026-21065 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21064CVE-2026-21064 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityHigh |
CVE-2026-21063CVE-2026-21063 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21062CVE-2026-21062 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21061CVE-2026-21061 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21060CVE-2026-21060 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21059CVE-2026-21059 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21058CVE-2026-21058 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published08/10/2026 | SeverityMedium |
CVE-2026-21038CVE-2026-21038 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Android USB Driver for Windows | Published06/05/2026 | SeverityMedium |
CVE-2026-21037CVE-2026-21037 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Members | Published06/05/2026 | SeverityMedium |
CVE-2026-21036CVE-2026-21036 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Internet | Published06/05/2026 | SeverityMedium |
CVE-2026-21035CVE-2026-21035 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Plus TV | Published06/05/2026 | SeverityMedium |
CVE-2026-21034CVE-2026-21034 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Auto | Published06/05/2026 | SeverityMedium |
CVE-2026-21033CVE-2026-21033 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Assistant | Published06/05/2026 | SeverityMedium |
CVE-2026-21032CVE-2026-21032 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Assistant | Published06/05/2026 | SeverityMedium |
CVE-2026-21031CVE-2026-21031 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21030CVE-2026-21030 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21029CVE-2026-21029 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21028CVE-2026-21028 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21027CVE-2026-21027 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21026CVE-2026-21026 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21025CVE-2026-21025 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-21017CVE-2026-21017 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published06/05/2026 | SeverityMedium |
CVE-2026-8915CVE-2026-8915 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/28/2026 | SeverityHigh |
CVE-2026-47317CVE-2026-47317 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47316CVE-2026-47316 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47315CVE-2026-47315 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47314CVE-2026-47314 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityHigh |
CVE-2026-47313CVE-2026-47313 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47312CVE-2026-47312 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47311CVE-2026-47311 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityHigh |
CVE-2026-47310CVE-2026-47310 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityHigh |
CVE-2026-47309CVE-2026-47309 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published05/19/2026 | SeverityMedium |
CVE-2026-47308CVE-2026-47308 | Exploitation statusNot known exploited | FixNot confirmed | Affected productWalrus | Published05/19/2026 | SeverityMedium |
CVE-2026-47307CVE-2026-47307 | Exploitation statusNot known exploited | FixNot confirmed | Affected productWalrus | Published05/19/2026 | SeverityMedium |
CVE-2026-21022CVE-2026-21022 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21021CVE-2026-21021 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21020CVE-2026-21020 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21018CVE-2026-21018 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21016CVE-2026-21016 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21015CVE-2026-21015 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityMedium |
CVE-2026-21023CVE-2026-21023 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/29/2026 | SeverityMedium |
CVE-2026-6839CVE-2026-6839 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-41667CVE-2026-41667 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-41666CVE-2026-41666 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-41665CVE-2026-41665 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-41664CVE-2026-41664 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-40450CVE-2026-40450 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-40449CVE-2026-40449 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-40448CVE-2026-40448 | Exploitation statusNot known exploited | FixNot confirmed | Affected productONE | Published04/22/2026 | SeverityMedium |
CVE-2026-21010CVE-2026-21010 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21008CVE-2026-21008 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-40447CVE-2026-40447 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityMedium |
CVE-2026-21014CVE-2026-21014 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Camera | Published04/13/2026 | SeverityMedium |
CVE-2026-21013CVE-2026-21013 | Exploitation statusNot known exploited | FixNot confirmed | Affected productGalaxy Wearable | Published04/13/2026 | SeverityMedium |
CVE-2026-21012CVE-2026-21012 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21011CVE-2026-21011 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21009CVE-2026-21009 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21007CVE-2026-21007 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21006CVE-2026-21006 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-21003CVE-2026-21003 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CVE-2026-40446CVE-2026-40446 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityMedium |
CVE-2026-25209CVE-2026-25209 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityMedium |
CVE-2026-25208CVE-2026-25208 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityHigh |
CVE-2026-25207CVE-2026-25207 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityHigh |
CVE-2026-25206CVE-2026-25206 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityMedium |
CVE-2026-25205CVE-2026-25205 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityHigh |
CVE-2026-25204CVE-2026-25204 | Exploitation statusNot known exploited | FixNot confirmed | Affected productEscargot | Published04/13/2026 | SeverityMedium |
CVE-2026-21005CVE-2026-21005 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published03/16/2026 | SeverityHigh |
CVE-2026-21004CVE-2026-21004 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published03/16/2026 | SeverityMedium |
CVE-2026-21002CVE-2026-21002 | Exploitation statusNot known exploited | FixNot confirmed | Affected productGalaxy Store | Published03/16/2026 | SeverityMedium |
CVE-2026-21001CVE-2026-21001 | Exploitation statusNot known exploited | FixNot confirmed | Affected productGalaxy Store | Published03/16/2026 | SeverityMedium |
CVE-2026-21000CVE-2026-21000 | Exploitation statusNot known exploited | FixNot confirmed | Affected productGalaxy Store | Published03/16/2026 | SeverityHigh |
CVE-2026-20999CVE-2026-20999 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmart Switch | Published03/16/2026 | SeverityHigh |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan
