vciy

CVE-2025-21027

INDEX BUILT · 2026-09-20

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Improper verification of intent by broadcast receiver in ImsService prior to SMR Sep-2025 Release 1 allows local attackers to temporarily disable the…

CVE-2025-210274 of 4 sources documented this
16

rank 16 = 0 + 11 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00108  ·  without this subject the record ranks 16

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.4, from NVD  ·  without this subject the record ranks 5

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 16

How much of the world it touches

NVD CPE configurations

4 products in the CPE ranges  ·  without this subject the record ranks 11

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 16

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2,310over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$2,310 = $4.99M incident cost x 0.42806422275080447 exposure x 0.00108 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.00108EPSSNOT IN KEVas of 2026-09-20
Severity5.1 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-09-03, 335 days at 0.00, as of 2026-08-04. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Sources disagree here.

Severity score
SamsungMobile5.1 MEDIUMreceipt
NVD4.4 MEDIUMreceipt

Both shown, dated. We don't pick winners. disagreement-rules@v1

Running Samsung Mobile Devices? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Set up a watchlist (needs a Practitioner account)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

AcceptDeferPatch by…Not affectedMitigated

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

Reachneeds local access · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-925 Improper Verification of Intent by Broadcast Receiverreceipt
Published consequencesCWE-925: Integrity: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inSMR Sep-2025 Release in Android 13, 14, 15, 16receipt
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

CVSS, the CNA5.1 MEDIUMreceipt
CVSS, NVD4.4 MEDIUMreceipt
Exploit probability0.00108 · top 99% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bySamsungMobilereceipt
Recorded changes14 · last 18 Sep 2026derived

Affected & Fixed Versions as published

Affected productSamsung Mobile Devicesreceipt
Published rangessamsung android 13.0; samsung android 14.0; samsung android 15.0; samsung android 16.0receipt
Fixed inSMR Sep-2025 Release in Android 13, 14, 15, 16receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Improper verification of intent by broadcast receiver in ImsService prior to SMR Sep-2025 Release 1 allows local attackers to temporarily disable the SIM. receipt

NVD's analysis a second authority

severity
4.4 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
affected versions
samsung android 13.0; samsung android 14.0; samsung android 15.0; and 1 more, listed in full below
also scored by
[email protected] 5.1 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

The CNA scored it 5.1 and NVD 4.4. Both are shown because both were published; we do not pick one.

check it yourself security.samsungmobile.com receipt

Movement the material steps

3 Sep 20250.00013
15 Jun 20260.00101 · scoring model v2026.06.15
4 Aug 20260.00108
Show all 14 observations
3 Sep 20250.00013
9 Sep 20250.00017
5 Oct 20250.0002
10 Nov 20250.00023
3 Jan 20260.00029
30 Jan 20260.00019
31 Jan 20260.00018
11 Feb 20260.0002
30 Mar 20260.00022
9 May 20260.00024
20 May 20260.00029
30 May 20260.0003
15 Jun 20260.00101
4 Aug 20260.00108

14 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00108Published2025-09-03Index as of2026-08-04

The record had been public for 11 months when this index was last written.

Published 2025-09-03 receipt · Index as of 2026-08-04 derived

Siblings and hubs

Records related to this one

Its defect family

samsung mobile devices

Of the 2 records in this family, this is the only one holding a stated fix version: SMR Sep-2025 Release in Android 13, 14, 15, 16.

Grouped by shared product and weakness, not by shared vulnerability. Each record's own state is on its own page.

Family membership: held values

This record is one of a group, and the group's page describes all of them. This page is kept and dated, and the defect family's own page is the one we offer for indexing: the whole group.

Browse the index from here

These are index-wide views, not findings about CVE-2025-21027.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.