vciy

CVE-2021-25409

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 access in Notification setting prior to SMR JUN-2021 Release 1 allows physically proximate attackers to set arbitrary notification via…

CVE-2021-254094 of 4 sources documented this
8

rank 8 = 0 + 6 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00104  ·  without this subject the record ranks 8

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 2.4, from NVD  ·  without this subject the record ranks 2

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 8

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 6

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1,250over 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

$1,250 = $4.99M incident cost x 0.24048551839932833 exposure x 0.00104 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.00104EPSSNOT IN KEVas of 2026-09-20
Severity2.4 LOWreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2021-06-12, 1829 days at 0.00, as of 2026-06-15. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-703, improper check or handling of exceptional conditions. The index holds 176 prior instances of this class, 3 KEV-listed. taxonomy@v1

Full pattern panel

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

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 physical access · no privileges required · no user interaction · low attack complexityreceipt
ImpactPartial integrity lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-703 Improper Check or Handling of Exceptional Conditionsreceipt
Published consequencesCWE-703: Confidentiality, Availability, Integrity: Read Application Data, DoS: Crash, Exit, or Restart, Unexpected State[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed inNo fix version in held sources, as the index stood on 15 Jun 2026.
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, NVD2.4 LOWreceipt
Exploit probability0.00104 · top 99% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bySamsung Mobilereceipt
Recorded changes13 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productSamsung Mobile Devicesreceipt
Published rangesgoogle android 10.0receipt

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 access in Notification setting prior to SMR JUN-2021 Release 1 allows physically proximate attackers to set arbitrary notification via physically configuring device. receipt

NVD's analysis a second authority

severity
2.4 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
weakness
CWE-703; CWE-862
affected versions
google android 10.0

check it yourself security.samsungmobile.com receipt

Movement the material steps

12 Jun 20210.00416
7 Mar 20234.6e-4 · scoring model v2023.03.01
17 Mar 20250.00018 · scoring model v2025.03.14
15 Jun 20260.00104 · scoring model v2026.06.15

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 13 observations
12 Jun 20210.00416
17 Jun 20210.00171
19 Jun 20210.00765
24 Jun 20210.00171
6 Jan 20220.00765
4 Feb 20220.01404
1 Apr 20220.00885
7 Mar 20234.6e-4
8 Mar 20230.00046
17 Mar 20250.00018
29 Mar 20250.00033
30 Mar 20250.00018
15 Jun 20260.00104

13 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.00104Published2021-06-11Index as of2026-06-15

Exploit probability more than doubled between 2021-06-17 and 2021-06-19 (0.00171 → 0.00765) and the record had been public for 5 years when this index was last written.

Published 2021-06-11 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-703, improper check or handling of exceptional conditions. The index holds 176 prior instances of this class, 3 KEV-listed. [email protected]

CVE-2021-25370 · Samsung Mobile Devicesmatches 4 of 10KEV listed · 2021receipt
CVE-2021-25372 · Samsung Mobile Devicesmatches 4 of 10KEV listed · 2021receipt
CVE-2022-22265 · Samsung Mobile Devicesmatches 2 of 10KEV listed · 2022receipt

176 records in this class held. The six above are ranked by exploit maturity, then recency.

Siblings and hubs

Records related to this one

Its defect family

samsung mobile devices

Of the 7 records in this advisory that state one, this holds the lowest NVD CVSS score: 2.4.

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-2021-25409.

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.