Samsung Mobile
Samsung Mobile is a provider of Samsung Android mobile devices and associated software components, including applications, native libraries, wearable components, and security platform components.
en
Samsung Mobile is a provider of Samsung Android mobile devices and associated software components, including applications, native libraries, wearable components, and security platform components.
Severity across 337 analyzed records
As of 09/11/2026, Samsung Mobile recorded 75 security vulnerabilities in the last 90 days across 19 products, including 19 rated High or above and 0 known exploited vulnerabilities (KEV) that should be prioritized for immediate remediation.
Over the last 90 days, Samsung Mobile Devices had the most security vulnerabilities in the Samsung Mobile ecosystem, with 50 vulnerabilities—approximately 66.67% of the provider's total vulnerabilities during this period.
| CVE | Exploitation status | Fix | Affected product | Published | Severity |
|---|---|---|---|---|---|
CVE-2026-21113CVE-2026-21113 | Exploitation statusNot known exploited | FixNot confirmed | Affected productVisual Voicemail | Published09/09/2026 | SeverityMedium |
CVE-2026-21112CVE-2026-21112 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Tips | Published09/09/2026 | SeverityMedium |
CVE-2026-21111CVE-2026-21111 | Exploitation statusNot known exploited | FixNot confirmed | Affected productlibsthmbc | Published09/09/2026 | SeverityMedium |
CVE-2026-21110CVE-2026-21110 | Exploitation statusNot known exploited | FixNot confirmed | Affected productlibsavscmn.so | Published09/09/2026 | SeverityMedium |
CVE-2026-21109CVE-2026-21109 | Exploitation statusNot known exploited | FixNot confirmed | Affected productWatch Plugin | Published09/09/2026 | SeverityLow |
CVE-2026-21108CVE-2026-21108 | Exploitation statusNot known exploited | FixNot confirmed | Affected productBixby Touch | Published09/09/2026 | SeverityMedium |
CVE-2026-21107CVE-2026-21107 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Notes | Published09/09/2026 | SeverityMedium |
CVE-2026-21106CVE-2026-21106 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Cloud Assistant | Published09/09/2026 | SeverityMedium |
CVE-2026-21105CVE-2026-21105 | Exploitation statusNot known exploited | FixNot confirmed | Affected productCollection | Published09/09/2026 | SeverityMedium |
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-21098CVE-2026-21098 | 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-21096CVE-2026-21096 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityCritical |
CVE-2026-21095CVE-2026-21095 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityCritical |
CVE-2026-21094CVE-2026-21094 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21093CVE-2026-21093 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21092CVE-2026-21092 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21091CVE-2026-21091 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21090CVE-2026-21090 | 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-21086CVE-2026-21086 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityMedium |
CVE-2026-21085CVE-2026-21085 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published09/09/2026 | SeverityHigh |
CVE-2026-21084CVE-2026-21084 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSmartThings | Published08/10/2026 | SeverityMedium |
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-21081CVE-2026-21081 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsungPassAutofill | 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-21075CVE-2026-21075 | Exploitation statusNot known exploited | FixNot confirmed | Affected productMy Galaxy | Published08/10/2026 | SeverityMedium |
CVE-2026-21074CVE-2026-21074 | Exploitation statusNot known exploited | FixNot confirmed | Affected productBixby | Published08/10/2026 | SeverityHigh |
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-21047CVE-2026-21047 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/28/2026 | SeverityHigh |
CVE-2026-21057CVE-2026-21057 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Pass | Published07/10/2026 | SeverityMedium |
CVE-2026-21056CVE-2026-21056 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Health | Published07/10/2026 | SeverityMedium |
CVE-2026-21055CVE-2026-21055 | Exploitation statusNot known exploited | FixNot confirmed | Affected productBixby | Published07/10/2026 | SeverityHigh |
CVE-2026-21054CVE-2026-21054 | Exploitation statusNot known exploited | FixNot confirmed | Affected productInputSharing | Published07/10/2026 | SeverityMedium |
CVE-2026-21053CVE-2026-21053 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Email | Published07/10/2026 | SeverityMedium |
CVE-2026-21052CVE-2026-21052 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21051CVE-2026-21051 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21050CVE-2026-21050 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21049CVE-2026-21049 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityHigh |
CVE-2026-21048CVE-2026-21048 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityHigh |
CVE-2026-21046CVE-2026-21046 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityHigh |
CVE-2026-21045CVE-2026-21045 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityHigh |
CVE-2026-21044CVE-2026-21044 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21043CVE-2026-21043 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21042CVE-2026-21042 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityHigh |
CVE-2026-21041CVE-2026-21041 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21040CVE-2026-21040 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/10/2026 | SeverityMedium |
CVE-2026-21039CVE-2026-21039 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published07/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-21024CVE-2026-21024 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung System Support Service | Published05/13/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-21019CVE-2026-21019 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published05/13/2026 | SeverityHigh |
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-21010CVE-2026-21010 | Exploitation statusNot known exploited | FixNot confirmed | Affected productSamsung Mobile Devices | Published04/13/2026 | SeverityMedium |
CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.
Explore CyStack VulnScan