vciy

CVE-2018-8545

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.

An information disclosure vulnerability exists in the way that Microsoft Edge handles cross-origin requests, aka "Microsoft Edge Information…

CVE-2018-85453 of 4 sources documented this
13

rank 13 = 1 + 11 + 1 + 0 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.05865  ·  without this subject the record ranks 12

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.3, from NVD  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2026-04-04  ·  without this subject the record ranks 12

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 13

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$70,400over the next 30 days, if this record is yours
Movement+$51,800on 2026-04-04, the last material move, 5 months before this reading
Basisassumeda published average, not your estate

$70,400 = $4.99M incident cost x 0.24048551839932833 exposure x 0.05865 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.05865EPSSNOT IN KEVas of 2026-09-20
Severity4.3 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementfallenreceipt
PLATEAU10Minimal movement since 2026-06-15, 83 days at 0.06, 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 Edge? 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.

Reachnetwork-reachable · no privileges required · user interaction required · low attack complexityreceipt
ImpactPartial confidentiality 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, NVD4.3 MEDIUMreceipt
Exploit probability0.05865 · top 7% of all CVEsreceipt
Assigned bymicrosoftreceipt
Recorded changes33 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Edgereceipt

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

An information disclosure vulnerability exists in the way that Microsoft Edge handles cross-origin requests, aka "Microsoft Edge Information Disclosure Vulnerability." This affects Microsoft Edge. receipt

NVD's analysis a second authority

severity
4.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

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

Dated events

2023-07-08EPSS moved 0.10 to 0.132025-03-29EPSS moved 0.04 to 0.202026-06-15EPSS moved 0.16 to 0.06

Movement the material steps

14 Apr 20210.08756
7 Mar 20230.09798 · scoring model v2023.03.01
8 Jul 20230.12844 · crossed 0.10
31 Jul 20230.09497 · crossed 0.10
17 Mar 20250.03502 · scoring model v2025.03.14
29 Mar 20250.19932 · crossed 0.10
30 Mar 20250.04 · crossed 0.10
4 Apr 20260.13153 · crossed 0.10
15 Jun 20260.05865 · crossed 0.10 · scoring model v2026.06.15
6 Sep 20260.05865
Show all 33 observations
14 Apr 20210.08756
4 Feb 20220.04004
10 May 20220.04794
20 Aug 20220.05274
26 Sep 20220.05853
6 Mar 20230.06416
7 Mar 20230.09798
27 Mar 20230.09962
11 Apr 20230.09798
8 Jul 20230.12844
31 Jul 20230.09497
19 Sep 20230.06937
7 Nov 20230.06776
6 Apr 20240.06097
3 Jul 20240.05321
29 Aug 20240.04549
24 Oct 20240.04238
17 Dec 20240.08547
17 Mar 20250.03502
19 Mar 20250.04
29 Mar 20250.19932
30 Mar 20250.04
30 Aug 20250.03927
15 Oct 20250.03785
8 Nov 20250.06705
8 Mar 20260.08835
4 Apr 20260.13153
2 May 20260.16473
15 Jun 20260.05865
23 Aug 20260.06311
30 Aug 20260.05865
5 Sep 20260.06311
6 Sep 20260.05865

33 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.05865Published2018-11-14Index as of2026-09-06

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

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

Siblings and hubs

Records related to this one

Its defect family

microsoft edge

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

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.