← console
voxell vciy

CVE-2025-21050

ROUTINE

Telemetry drift only. No threshold crossed and no authority ruling changed.

CVE record, CISA KEV and EPSS as of 2026-10-18.

CVEs like this one computed, by meaning

What to do now held facts and links

  1. Upgrade to SMR Oct-2025 Release in Android 13, 14, 15 or later CVE record
  2. Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
  3. Check your version against the ranges this record publishes.

What it is stated by the CNA

Improper input validiation in Contacts prior to SMR Oct-2025 Release 1 allows local attackers to access data across multiple user profiles.

weakness
CWE-20: Improper Input Validation
affected
Samsung Mobile Devices
published ranges
samsung android 13.0; samsung android 13.0-smr-apr-2022-r1; samsung android 13.0-smr-apr-2023-r1; samsung android 13.0-smr-apr-2024-r1; and 100 more on the CVE page
fixed in
SMR Oct-2025 Release in Android 13, 14, 15
severity
7.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
assigned by
SamsungMobile
published
2025-10-10

check us security.samsungmobile.com

Exploit code held, dated

exploit code
None held in the PoC-in-GitHub feed. A public repository changes this brief.

What moved held, dated

dateEPSSevent
10 Oct 20250.00018
16 Oct 20250.00022
24 Oct 20250.00028
11 Nov 20250.00032
17 Dec 20250.00037
9 Feb 20260.00045
8 Mar 20260.00029
9 Mar 20260.00028
20 Mar 20260.00022
6 May 20260.00025
15 Jun 20260.00117scoring model v2026.06.15
6 Jul 20260.0012
10 Sep 20260.00129

13 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.

Outside the record researched, cited

This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.

Sign in to add the researched section

What would change this brief held, dated

CISA KEV
Not listed in the catalogue we hold. A listing changes this brief.
exploit probability
0.00 on 2026-09-10 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
fix
Held: SMR Oct-2025 Release in Android 13, 14, 15. A newer fix from the CNA or OSV changes this brief.

Watch this CVE What counts as a move

How to check this

Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:

SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2025-21050', '2026-11-01T23:59:59.999999Z', now());