vciy

CVE-2023-33145

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 Edge (Chromium-based) Information Disclosure Vulnerability

CVE-2023-331454 of 4 sources documented this
20

rank 20 = 2 + 16 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.08619  ·  without this subject the record ranks 18

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 6.5, from the CNA  ·  without this subject the record ranks 4

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 20

How much of the world it touches

NVD CPE configurations

1 product 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 20

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$263,000over the next 30 days, if this record is yours
Movement-$264,000on 2025-11-21, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$263,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.08619 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.08619EPSSNOT IN KEVas of 2026-09-20
Severity6.5 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2025-03-30, 442 days at 0.09, as of 2026-06-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 Edge (Chromium-based)? 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
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA'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 in114.0.1823.51receipt
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 CNA6.5 MEDIUMreceipt
Exploit probability0.08619 · top 5% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned bymicrosoftreceipt
Recorded changes39 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productMicrosoft Edge (Chromium-based)receipt
Published rangesmicrosoft edge chromium < 114.0.1823.51receipt
Fixed in114.0.1823.51receipt

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

Microsoft Edge (Chromium-based) Information Disclosure Vulnerability receipt

NVD's analysis a second authority

affected versions
microsoft edge chromium < 114.0.1823.51
also scored by
[email protected] 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

check it yourself msrc.microsoft.com receipt

Dated events

2025-03-17EPSS moved 0.00 to 0.122025-03-29EPSS moved 0.13 to 0.562025-11-21EPSS moved 0.13 to 0.05

Movement the material steps

14 Jun 20230.00087
17 Mar 20250.11775 · crossed 0.10 · scoring model v2025.03.14
29 Mar 20250.56141 · crossed 0.50
30 Mar 20250.13267 · crossed 0.50
15 Apr 20250.07104 · crossed 0.10
18 Nov 20250.13267 · crossed 0.10
21 Nov 20250.0461 · crossed 0.10
15 Jun 20260.08619 · scoring model v2026.06.15
Show all 39 observations
14 Jun 20230.00087
22 Jun 20230.00106
20 Jul 20230.01698
15 Sep 20230.01925
16 Oct 20230.02365
23 Oct 20230.01727
24 Nov 20230.01145
19 Dec 20230.02714
27 Dec 20230.01138
20 Jan 20240.01380
3 Mar 20240.01207
19 Apr 20240.01490
2 May 20240.00816
13 May 20240.00765
19 Jun 20240.00781
15 Jul 20240.00937
27 Jul 20240.00865
22 Aug 20240.01067
30 Sep 20240.01438
10 Nov 20240.01425
23 Nov 20240.01985
17 Dec 20240.00229
1 Jan 20250.00126
3 Jan 20250.00179
17 Mar 20250.11775
19 Mar 20250.11668
25 Mar 20250.13267
29 Mar 20250.56141
30 Mar 20250.13267
15 Apr 20250.07104
22 May 20250.07284
4 Jun 20250.07104
10 Oct 20250.0461
18 Nov 20250.13267
21 Nov 20250.0461
8 Dec 20250.07104
8 Mar 20260.07436
14 Jun 20260.08107
15 Jun 20260.08619

39 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.08619Published2023-06-13Index as of2026-06-15

The record had been public for 3 years when this index was last written.

Published 2023-06-13 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Its defect family

microsoft edge

Of the 16 records in this family, this is the only one holding a stated fix version: 114.0.1823.51.

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

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-2023-33145.

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.