Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY29 SECURITY RECORDS

Samsung Mobile

Galaxy Store

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-21002 16 Mar 2026 See the vendor and CVE records for the affected range. 4.6.03.8 Update reference ↗
CVE-2026-21001 16 Mar 2026 See the vendor and CVE records for the affected range. 4.6.03.8 Update reference ↗
CVE-2026-21000 16 Mar 2026 See the vendor and CVE records for the affected range. 4.6.03.8 Update reference ↗
CVE-2026-20976 9 Jan 2026 See the vendor and CVE records for the affected range. 4.6.02 Update reference ↗
CVE-2023-21483 3 Sep 2025 See the vendor and CVE records for the affected range. 4.5.53.6 Update reference ↗
CVE-2025-20951 8 Apr 2025 See the vendor and CVE records for the affected range. 4.5.90.7 Update reference ↗
CVE-2025-20895 4 Feb 2025 See the vendor and CVE records for the affected range. 4.5.87.6 Update reference ↗
CVE-2024-20870 7 May 2024 See the vendor and CVE records for the affected range. 4.5.71.8 Update reference ↗
CVE-2024-20825 6 Feb 2024 See the vendor and CVE records for the affected range. 4.5.63.6 Update reference ↗
CVE-2024-20824 6 Feb 2024 See the vendor and CVE records for the affected range. 4.5.63.6 Update reference ↗
CVE-2024-20823 6 Feb 2024 See the vendor and CVE records for the affected range. 4.5.63.6 Update reference ↗
CVE-2024-20822 6 Feb 2024 See the vendor and CVE records for the affected range. 4.5.63.6 Update reference ↗
CVE-2023-42581 5 Dec 2023 See the vendor and CVE records for the affected range. 4.5.64.4 Update reference ↗
CVE-2023-42580 5 Dec 2023 See the vendor and CVE records for the affected range. 4.5.64.4 Update reference ↗
CVE-2023-30705 10 Aug 2023 See the vendor and CVE records for the affected range. 4.5.56.6 Update reference ↗
CVE-2023-21516 26 May 2023 unspecified < 4.5.49.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-21515 26 May 2023 unspecified < 4.5.49.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-21514 26 May 2023 unspecified < 4.5.49.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-21434 9 Feb 2023 unspecified < 4.5.49.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-21433 9 Feb 2023 unspecified < 4.5.49.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-33710 11 Jul 2022 unspecified < 4.5.41.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-33709 11 Jul 2022 unspecified < 4.5.41.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-33708 11 Jul 2022 unspecified < 4.5.41.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28791 3 May 2022 - < 4.5.41.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28776 11 Apr 2022 - < 4.5.36.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28544 11 Apr 2022 - < 4.5.40.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28542 11 Apr 2022 - < 4.5.40.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-22288 7 Jan 2022 - < 4.5.36.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-25499 6 Oct 2021 - < 4.5.32.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.