vciy

CVE-2018-8161

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 Office software when the software fails to properly handle objects in memory, aka…

CVE-2018-81614 of 4 sources documented this
33

rank 33 = 5 + 20 + 0 + 8 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.21697  ·  without this subject the record ranks 28

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 13

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 33

How much of the world it touches

NVD CPE configurations

11 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 33

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$1.08Mover the next 30 days, if this record is yours
Movement+$2.60Mon 2024-12-17, the last material move, 1 year, 8 months before this reading
Basisassumeda published average, not your estate

$1.08M = $4.99M incident cost x 1 exposure x 0.21697 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.21697EPSSNOT IN KEVas of 2026-09-20
Severity7.8 HIGHreceipt
Harmtotal lossreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementsteadyreceipt
PLATEAU10Minimal movement since 2026-06-15, 92 days at 0.22, as of 2026-09-15. 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 Word? 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 15 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.21697 · top 2% of all CVEsreceipt
Blast breadth4 products across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes44 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Word; Microsoft Office; Microsoft SharePointreceipt
Published rangesmicrosoft office 2010; microsoft office 2013; microsoft office 2016; microsoft office web apps 2010receipt
Show all 11 published ranges
microsoft office 2010
microsoft office 2013
microsoft office 2016
microsoft office web apps 2010
microsoft office web apps 2013
microsoft sharepoint server 2010
microsoft sharepoint server 2013
microsoft sharepoint server 2016
microsoft word 2010
microsoft word 2013
microsoft word 2016

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 Office software when the software fails to properly handle objects in memory, aka "Microsoft Office Remote Code Execution Vulnerability." This affects Microsoft Word, Word, Microsoft Office, Microsoft SharePoint. This CVE ID is unique from CVE-2018-8157, CVE-2018-8158. 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 office 2010; microsoft office 2013; microsoft office 2016; and 8 more, listed in full below

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

Dated events

2023-03-07EPSS moved 0.39 to 0.052025-03-17EPSS moved 0.80 to 0.152026-06-15EPSS moved 0.32 to 0.20

Movement the material steps

14 Apr 20210.17549
25 Apr 20220.31104
7 Mar 20230.0533 · crossed 0.10 · scoring model v2023.03.01
27 Dec 20230.10346 · crossed 0.10
22 Feb 20240.09173 · crossed 0.10
18 Mar 20240.15028 · crossed 0.10
18 Apr 20240.25893
17 Dec 20240.79665 · crossed 0.50
17 Mar 20250.15146 · crossed 0.50 · scoring model v2025.03.14
29 Mar 20250.26146
30 Mar 20250.15146
31 Aug 20250.28958
15 Jun 20260.20262 · scoring model v2026.06.15
15 Sep 20260.21697
Show all 44 observations
14 Apr 20210.17549
4 Feb 20220.21361
13 Feb 20220.23099
22 Mar 20220.27139
25 Apr 20220.31104
9 Jun 20220.32419
30 Aug 20220.34599
3 Feb 20230.3932
7 Mar 20230.0533
8 Mar 20230.05330
3 May 20230.06264
18 Aug 20230.06636
30 Sep 20230.07573
21 Oct 20230.09481
27 Dec 20230.10346
23 Jan 20240.10495
22 Feb 20240.09173
18 Mar 20240.15028
18 Apr 20240.25893
24 May 20240.29279
23 Sep 20240.29498
10 Dec 20240.27657
17 Dec 20240.79665
17 Mar 20250.15146
29 Mar 20250.26146
30 Mar 20250.15146
9 Apr 20250.14675
3 May 20250.23487
31 Aug 20250.28958
27 Sep 20250.31196
25 Oct 20250.3391
13 Dec 20250.37198
20 Dec 20250.32436
27 Dec 20250.3391
28 Dec 20250.32436
15 Jun 20260.20262
14 Jul 20260.20302
1 Aug 20260.21535
14 Aug 20260.22109
23 Aug 20260.19919
30 Aug 20260.22109
5 Sep 20260.19919
6 Sep 20260.22109
15 Sep 20260.21697

44 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.21697Published2018-05-09Index as of2026-09-15

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

Published 2018-05-09 receipt · Index as of 2026-09-15 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft word

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

Family membership: held values

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-2018-8161.

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.