vciy

CVE-2020-1483

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.

Microsoft Outlook Memory Corruption Vulnerability

CVE-2020-14834 of 4 sources documented this
30

rank 30 = 2 + 23 + 0 + 5 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.08844  ·  without this subject the record ranks 28

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 9.3, from NVD  ·  without this subject the record ranks 7

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 30

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$270,000over the next 30 days, if this record is yours
Movement+$210,000on 2025-05-17, the last material move, 1 year, 2 months before this reading
Basisassumeda published average, not your estate

$270,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.08844 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.08844EPSSNOT IN KEVas of 2026-09-20
Severity5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2026-06-15, 51 days at 0.09, as of 2026-08-05. arc-rules@v1

Foresight · where to check next

Microsoft WindowsMicrosoft Windows1483

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 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

Sources disagree here.

Severity score
Microsoft5 MEDIUMreceipt
NVD9.3 CRITICALreceipt
Scoring standard
MicrosoftCVSS v3.1receipt
NVDCVSS v2.0receipt

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

Running Microsoft Office 2019? 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 · low privileges required · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-787 Out-of-bounds Writereceipt
Published consequencesCWE-787: Integrity: Modify Memory, Execute Unauthorized Code or Commands; Availability: DoS: Crash, Exit, or Restart; Other: 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 5 Aug 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, the CNA5 MEDIUMreceipt
CVSS, NVD9.3 CRITICALreceipt
Exploit probability0.08844 · top 5% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes45 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Office 2019; Microsoft 365 Apps for Enterprise; Microsoft Outlook 2016; Microsoft Outlook 2013 Service Pack 1; Microsoft Outlook 2010 Service Pack 2receipt
Published rangesmicrosoft office 2019; microsoft outlook 2010; microsoft outlook 2013; microsoft outlook 2016receipt

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

A remote code execution vulnerability exists in Microsoft Outlook when the software fails to properly handle objects in memory. An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user. If the current user is logged on with administrative user rights, an attacker could take control of the affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. receipt

Read the rest of the CNA's description

Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. Exploitation of the vulnerability requires that a user open a specially crafted file with an affected version of Microsoft Outlook software. In an email attack scenario, an attacker could exploit the vulnerability by sending the specially crafted file to the user and convincing the user to open the file. In a web-based attack scenario, an attacker could host a website (or leverage a compromised website that accepts or hosts user-provided content) that contains a specially crafted file designed to exploit the vulnerability. An attacker would have no way to force users to visit the website. Instead, an attacker would have to convince users to click a link, typically by way of an enticement in an email or instant message, and then convince them to open the specially crafted file. Note that where severity is indicated as Critical in the Affected Products table, the Preview Pane is an attack vector. The security update addresses the vulnerability by correcting how Outlook handles objects in memory.

NVD's analysis a second authority

severity
9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C
weakness
CWE-787
affected versions
microsoft office 2019; microsoft outlook 2010; microsoft outlook 2013; and 1 more, listed in full below
also scored by
[email protected] 5 CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N · [email protected] 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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

check it yourself portal.msrc.microsoft.com receipt

Dated events

2022-01-06EPSS moved 0.08 to 0.282022-04-01EPSS moved 0.38 to 0.022026-06-15EPSS moved 0.19 to 0.09

Movement the material steps

14 Apr 20210.07953
6 Jan 20220.27938 · crossed 0.10
1 Apr 20220.01875 · crossed 0.10
7 Mar 20230.038 · scoring model v2023.03.01
17 Mar 20250.02703 · scoring model v2025.03.14
29 Mar 20250.2284 · crossed 0.10
30 Mar 20250.07297 · crossed 0.10
17 May 20250.14188 · crossed 0.10
15 Jun 20260.08876 · crossed 0.10 · scoring model v2026.06.15
5 Aug 20260.08844
Show all 45 observations
14 Apr 20210.07953
6 Jan 20220.27938
4 Feb 20220.3577
5 Mar 20220.37706
1 Apr 20220.01875
7 Mar 20230.038
8 Mar 20230.03800
12 Mar 20230.03285
24 Mar 20230.03507
7 Apr 20230.03989
20 Apr 20230.03507
3 May 20230.03524
24 Jul 20230.03711
20 Sep 20230.04342
4 Oct 20230.03066
4 Dec 20230.03027
21 Dec 20230.02819
4 Jan 20240.00234
5 Jan 20240.00176
10 Jan 20240.00330
21 Jan 20240.00312
14 Mar 20240.00329
16 Apr 20240.00373
4 May 20240.00529
19 May 20240.00380
6 Jun 20240.00466
21 Jun 20240.00474
8 Jul 20240.00468
10 Aug 20240.00341
26 Sep 20240.00426
12 Oct 20240.00424
27 Oct 20240.00459
17 Dec 20240.02411
17 Mar 20250.02703
19 Mar 20250.03558
25 Mar 20250.07652
29 Mar 20250.2284
30 Mar 20250.07297
17 May 20250.14188
8 Jul 20250.16968
18 Nov 20250.13972
21 Nov 20250.16968
17 Dec 20250.19035
15 Jun 20260.08876
5 Aug 20260.08844

45 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.08844Published2020-08-17Index as of2026-08-05

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

Published 2020-08-17 receipt · Index as of 2026-08-05 derived

The pattern, elsewhere

This record is one instance of CWE-787, out-of-bounds write. The index holds 14893 prior instances of this class, 164 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2024-30051 · Microsoft Windows 10 Version 1809matches 6 of 9KEV listed · 2024receipt
CVE-2023-23376 · Microsoft Windows 10 Version 1507matches 6 of 9KEV listed · 2023receipt
CVE-2023-28252 · Microsoft Windows 10 Version 1809matches 6 of 9KEV listed · 2023receipt
CVE-2022-24521 · Microsoft Windows 10 Version 1809matches 6 of 9KEV listed · 2022receipt
CVE-2022-37969 · Microsoft Windows 10 Version 1809matches 6 of 9KEV listed · 2022receipt
CVE-2022-41073 · Microsoft Windows 10 Version 1507matches 6 of 9KEV listed · 2022receipt

"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

14893 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

Its defect family

microsoft office 2019

Of the 4 records in this family that state one, this holds the highest NVD CVSS score: 9.3.

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-2020-1483.

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.