vciy

CVE-2020-9686

INDEX BUILT · 2026-10-18

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.

Adobe Photoshop versions Photoshop CC 2019, and Photoshop 2020 have an out-of-bounds read vulnerability

CVE-2020-96864 of 4 sources documented this
22

rank 22 = 1 + 16 + 1 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.04235  ·  without this subject the record ranks 21

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from NVD  ·  without this subject the record ranks 6

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-09-18  ·  without this subject the record ranks 21

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 18

Someone else already set the date

CISA KEV remediation due date

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

Hindsight · the state

0.04235EPSSNOT IN KEVas of 2026-10-18
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
FALLING10Fallen from 0.36324 to 0.04235 across 29 observations. arc-rules@v1

Foresight · where to check next

Apple macOSApple SafariCVE-2014-0160Microsoft WindowsCVE-2016-1646Google Chrome9686

This record is one instance of CWE-125, out-of-bounds read. The index holds 10268 prior instances of this class, 19 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Adobe Photoshop? 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

Watch Adobe Photoshop

Set up a watchlist (free with an account: one stack of three products)

Record your call

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

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

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.

Reachnetwork-reachable · no privileges required · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-125 Out-of-bounds Readreceipt
Published consequencesCWE-125: Confidentiality: Read Memory; Confidentiality: Bypass Protection Mechanism; Availability: DoS: Crash, Exit, or Restart; Other: Varies by Contextcwe-consequences@4.20

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.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

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.5 MEDIUMreceipt
Exploit probability0.04235 · top 9% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byadobereceipt
Recorded changes29 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productAdobe Photoshopreceipt
Published rangesadobe photoshop <= 21.2; adobe photoshop cc <= 20.0.9receipt

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.

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$129,000over the next 30 days, if this record is yours
Movement-$918,000on 2022-04-01, the last material move, 4 years, 2 months before this reading
Basisassumeda published average, not your estate

$129,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.04235 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.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Adobe Photoshop versions Photoshop CC 2019, and Photoshop 2020 have an out-of-bounds read vulnerability. Successful exploitation could lead to arbitrary code execution. receipt

NVD's analysis a second authority

severity
6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
weakness
CWE-125
affected versions
adobe photoshop <= 21.2; adobe photoshop cc <= 20.0.9

check it yourself helpx.adobe.com receipt

Dated events

2022-01-06EPSS moved 0.36 to 0.722022-02-04EPSS moved 0.72 to 0.312026-06-15EPSS moved 0.23 to 0.04

Movement the material steps

14 Apr 20210.36324
6 Jan 20220.71906 · crossed 0.50
4 Feb 20220.31326 · crossed 0.50
1 Apr 20220.01282 · crossed 0.10
7 Mar 20230.00459 · scoring model v2023.03.01
17 Mar 20250.12009 · crossed 0.10 · scoring model v2025.03.14
18 Sep 20250.23037
15 Jun 20260.04235 · crossed 0.10 · scoring model v2026.06.15
Show all 29 observations
14 Apr 20210.36324
6 Jan 20220.71906
4 Feb 20220.31326
1 Apr 20220.01282
7 Mar 20230.00459
7 Apr 20230.00536
21 Apr 20230.00904
31 May 20230.01287
14 Jun 20230.01269
28 Jun 20230.01339
26 Jul 20230.01125
9 Aug 20230.00964
23 Sep 20230.00752
25 Nov 20230.00511
10 Dec 20230.00519
17 Feb 20240.00539
5 Mar 20240.00586
26 May 20240.00547
31 Aug 20240.00645
1 Oct 20240.00792
7 Mar 20250.00892
17 Mar 20250.12009
19 Mar 20250.18326
25 Mar 20250.14355
29 Mar 20250.20105
30 Mar 20250.14355
9 Aug 20250.18326
18 Sep 20250.23037
15 Jun 20260.04235

29 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.04235Published2020-07-22Index as of2026-06-15

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

Published 2020-07-22 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-125, out-of-bounds read. The index holds 10268 prior instances of this class, 19 KEV-listed. The nearest of its KEV-listed records are drawn beside this. cwe-consequences@4.20

CVE-2023-28204 · Apple macOSmatches 8 of 9KEV listed · 2023receipt
CVE-2023-42916 · Apple Safarimatches 8 of 9KEV listed · 2023receipt
CVE-2014-0160matches 7 of 8KEV listed · 2014receipt
CVE-2025-24991 · Microsoft Windows 10 Version 1507matches 7 of 9KEV listed · 2025receipt
CVE-2016-1646matches 6 of 8KEV listed · 2016receipt
CVE-2026-11645 · Google Chromematches 6 of 9KEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

10268 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

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

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

These are index-wide views, not findings about CVE-2020-9686.

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.