vciy

CVE-2018-8597

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.

A remote code execution vulnerability exists in Microsoft Excel software when the software fails to properly handle objects in memory, aka "Microsoft…

CVE-2018-85974 of 4 sources documented this
30

rank 30 = 4 + 20 + 0 + 6 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.16130  ·  without this subject the record ranks 26

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 7.8, from NVD  ·  without this subject the record ranks 10

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

6 products in the CPE ranges  ·  without this subject the record ranks 24

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$805,000over the next 30 days, if this record is yours
Movement-$987,000on 2025-03-30, the last material move, 1 year, 5 months before this reading
Basisassumeda published average, not your estate

$805,000 = $4.99M incident cost x 1 exposure x 0.1613 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.1613EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2026-05-30, 99 days at 0.16, as of 2026-09-06. 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

Running Microsoft Office? 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 · user interaction required · low attack complexityreceipt
ImpactComplete confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.0 · NVD's vectorreceipt
Weakness classNo CWE mapping in held sources.

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 6 Sep 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, NVD7.8 HIGHreceipt
Exploit probability0.1613 · top 3% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes47 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Office; Microsoft Excelreceipt
Published rangesmicrosoft excel 2010; microsoft excel 2013; microsoft excel 2016; microsoft office 2010receipt
Show all 6 published ranges
microsoft excel 2010
microsoft excel 2013
microsoft excel 2016
microsoft office 2010
microsoft office 2016
microsoft office 2019

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 Excel software when the software fails to properly handle objects in memory, aka "Microsoft Excel Remote Code Execution Vulnerability." This affects Office 365 ProPlus, Microsoft Office, Microsoft Excel. This CVE ID is unique from CVE-2018-8636. receipt

NVD's analysis a second authority

severity
7.8 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
affected versions
microsoft excel 2010; microsoft excel 2013; microsoft excel 2016; and 3 more, listed in full below

check it yourself portal.msrc.microsoft.com securityfocus.com receipt

Dated events

2022-02-04EPSS moved 0.14 to 0.062025-03-17EPSS moved 0.01 to 0.262026-06-15EPSS moved 0.25 to 0.16

Movement the material steps

14 Apr 20210.13741
4 Feb 20220.05698 · crossed 0.10
24 Oct 20220.10253 · crossed 0.10
7 Mar 20230.01127 · crossed 0.10 · scoring model v2023.03.01
17 Mar 20250.26322 · crossed 0.10 · scoring model v2025.03.14
25 Mar 20250.40025
29 Mar 20250.598 · crossed 0.50
30 Mar 20250.40025 · crossed 0.50
18 Nov 20250.29762
15 Jun 20260.1613 · scoring model v2026.06.15
6 Sep 20260.1613
Show all 47 observations
14 Apr 20210.13741
4 Feb 20220.05698
7 Jun 20220.07289
17 Sep 20220.07999
24 Oct 20220.10253
27 Nov 20220.12163
11 Jan 20230.12826
7 Mar 20230.01127
22 Mar 20230.01489
24 Apr 20230.02098
9 May 20230.02418
24 May 20230.01950
24 Jun 20230.03831
7 Jul 20230.02360
27 Jul 20230.02394
8 Aug 20230.01702
28 Aug 20230.02394
11 Sep 20230.03006
23 Dec 20230.01923
5 Mar 20240.01534
22 Mar 20240.01788
4 May 20240.02236
25 May 20240.01894
7 Jul 20240.01772
27 Aug 20240.02492
21 Oct 20240.05086
21 Nov 20240.07372
17 Dec 20240.01641
27 Dec 20240.01461
17 Mar 20250.26322
19 Mar 20250.3366
25 Mar 20250.40025
29 Mar 20250.598
30 Mar 20250.40025
11 Jun 20250.3681
12 Jun 20250.35597
30 Oct 20250.31163
3 Nov 20250.31336
18 Nov 20250.29762
21 Nov 20250.31336
2 May 20260.27717
30 May 20260.24675
15 Jun 20260.1613
23 Aug 20260.1452
30 Aug 20260.1613
5 Sep 20260.1452
6 Sep 20260.1613

47 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.1613Published2018-12-12Index as of2026-09-06

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

Published 2018-12-12 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2018-8597.

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.