vciy

CVE-2020-9946

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.

This issue was addressed with improved checks

CVE-2020-99464 of 4 sources documented this
22

rank 22 = 0 + 17 + 0 + 5 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00307  ·  without this subject the record ranks 22

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.8, 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 22

How much of the world it touches

NVD CPE configurations

3 products in the CPE ranges  ·  without this subject the record ranks 17

Someone else already set the date

CISA KEV remediation due date

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

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

$15,300 = $4.99M incident cost x 1 exposure x 0.00307 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.00307EPSSNOT IN KEVas of 2026-09-20
Severity6.8 MEDIUMreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2021-04-14, 1914 days at 0.00, as of 2026-07-11. arc-rules@v1

Foresight · where to check next

This record is one instance of CWE-667, improper locking. The index holds 739 prior instances of this class, 2 KEV-listed. taxonomy@v1

Full pattern panel

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

Running Apple iOS? 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
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-667 Improper Lockingreceipt
Published consequencesCWE-667: Availability: DoS: Resource Consumption (CPU)[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchipados 14.0; watchos 7.0; iphone os 14.0receipt
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, NVD6.8 MEDIUMreceipt
Exploit probability0.00307 · top 76% of all CVEsreceipt
Blast breadth3 products across 1 vendorderived
Assigned byapplereceipt
Recorded changes19 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productApple iOS; Apple watchOSreceipt
Published rangesapple ipados < 14.0; apple iphone os < 14.0; apple watchos < 7.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

This issue was addressed with improved checks. This issue is fixed in iOS 14.0 and iPadOS 14.0, watchOS 7.0. The screen lock may not engage after the specified time period. receipt

NVD's analysis a second authority

severity
6.8 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
weakness
CWE-667
affected versions
apple ipados < 14.0; apple iphone os < 14.0; apple watchos < 7.0

check it yourself support.apple.com support.apple.com seclists.org seclists.org receipt

Movement the material steps

14 Apr 20210.00153
7 Mar 20237.6e-4 · scoring model v2023.03.01
17 Mar 20250.00122 · scoring model v2025.03.14
15 Jun 20260.00303 · scoring model v2026.06.15
11 Jul 20260.00307
Show all 19 observations
14 Apr 20210.00153
6 Jan 20220.00685
4 Feb 20220.01787
1 Apr 20220.01018
7 Mar 20237.6e-4
8 Mar 20230.00076
27 Apr 20230.00079
23 May 20230.00080
2 Jul 20230.00091
5 Aug 20240.00108
20 Aug 20240.00150
17 Dec 20240.00105
17 Mar 20250.00122
29 Mar 20250.00147
30 Mar 20250.00122
7 Apr 20250.00116
10 Apr 20250.00057
15 Jun 20260.00303
11 Jul 20260.00307

19 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.00307Published2020-10-16Index as of2026-07-11

The record had been public for 5 years, 8 months when this index was last written.

Published 2020-10-16 receipt · Index as of 2026-07-11 derived

The pattern, elsewhere

This record is one instance of CWE-667, improper locking. The index holds 739 prior instances of this class, 2 KEV-listed. [email protected]

CVE-2025-43510 · Apple iOS and iPadOSmatches 7 of 9KEV listed · 2025receipt
CVE-2021-1782 · Apple iOS and iPadOSmatches 6 of 9KEV listed · 2021receipt

739 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

apple ios

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

Family membership: computed, pro@dim2000

Nothing we hold separates this record from the others in its defect family. 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-2020-9946.

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.