vciy

CVE-2025-2783

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.

Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to…

CVE-2025-27833 of 4 sources documented this
51

rank 51 = 40 + 0 + 3 + 2 + 6

rank@v1 · this cycle

Someone is already using it

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

EPSS 0.09238 · CISA KEV listed  ·  without this subject the record ranks 11

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 51

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

rose on 2025-12-18  ·  without this subject the record ranks 48

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 49

Someone else already set the date

CISA KEV remediation due date

CISA remediation date held  ·  without this subject the record ranks 45

Hindsight · the state

0.09238EPSSKEV · LISTED
Severitynot scored
Harmnot stated
Exploitationin the wild · KEVreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2026-06-15, 81 days at 0.09, as of 2026-09-04. 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 Google Chrome? 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.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classNo CWE mapping in held sources.
Ransomware campaign useUnknown to CISAreceipt

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed in134.0.6998.177receipt
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.
CISA remediation statusoverdue since 2025-04-17receipt
CISA required actionApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.receipt
Published to CISA KEV1 dayderived

Exploit Status & Known PoCs a ladder, not a score

Current rung: Exploited in the wild · CISA KEV listed, 2025-03-27.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published · 5 public repositories2025-04-06receipt
  • RUNG 3Exploited in the wild · CISA KEV listed2025-03-27receipt
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.09238 · top 5% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byChromereceipt
Recorded changes83 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productGoogle Chromereceipt
Published rangesgoogle chrome < 134.0.6998.177receipt
Fixed in134.0.6998.177receipt

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

Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6998.177 allowed a remote attacker to perform a sandbox escape via a malicious file. (Chromium security severity: High) receipt

NVD's analysis a second authority

affected versions
google chrome < 134.0.6998.177
also scored by
8.3 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

check it yourself chromereleases.googleblog.com issues.chromium.org receipt

Dated events

2025-03-27Added to CISA KEV2025-03-28EPSS moved 0.02 to 0.092025-04-17CISA remediation due2025-11-18EPSS moved 0.27 to 0.802026-06-15EPSS moved 0.45 to 0.09

Movement the material steps

27 Mar 20250.01618
29 Mar 20250.13978 · crossed 0.10
30 Mar 20250.09588 · crossed 0.10
1 Apr 20250.13075 · crossed 0.10
15 Apr 20250.01625 · crossed 0.10
12 Aug 20250.28801 · crossed 0.10
18 Nov 20250.8031 · crossed 0.50
21 Nov 20250.29849 · crossed 0.50
18 Dec 20250.44438
18 Feb 20260.50098 · crossed 0.50
19 Feb 20260.48351 · crossed 0.50
9 Mar 20260.35406
3 May 20260.46566
15 Jun 20260.08682 · crossed 0.10 · scoring model v2026.06.15
2 Sep 20260.09238

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 69 observations
27 Mar 20250.01618
28 Mar 20250.09213
29 Mar 20250.13978
30 Mar 20250.09588
1 Apr 20250.13075
13 Apr 20250.15142
15 Apr 20250.01625
20 Apr 20250.02011
27 Apr 20250.02941
15 May 20250.03941
16 May 20250.0679
2 Jun 20250.07733
15 Jun 20250.07481
17 Jun 20250.06256
20 Jun 20250.05464
28 Jun 20250.07239
18 Jul 20250.08309
26 Jul 20250.07186
12 Aug 20250.28801
21 Aug 20250.19786
16 Sep 20250.2403
18 Sep 20250.19786
24 Sep 20250.22568
10 Oct 20250.23981
17 Oct 20250.22568
22 Oct 20250.25259
25 Oct 20250.27196
18 Nov 20250.8031
21 Nov 20250.29849
22 Nov 20250.24989
18 Dec 20250.44438
20 Dec 20250.43359
21 Dec 20250.38105
29 Dec 20250.36142
1 Jan 20260.38105
10 Feb 20260.40048
11 Feb 20260.44722
18 Feb 20260.50098
19 Feb 20260.48351
21 Feb 20260.46236
22 Feb 20260.4165
1 Mar 20260.46236
2 Mar 20260.43678
4 Mar 20260.39116
5 Mar 20260.4086
9 Mar 20260.35406
11 Mar 20260.36259
21 Mar 20260.39478
27 Mar 20260.35587
30 Mar 20260.39478
19 Apr 20260.44146
22 Apr 20260.39478
29 Apr 20260.38606
30 Apr 20260.44146
1 May 20260.38606
3 May 20260.46566
5 May 20260.44549
8 May 20260.47451
9 May 20260.4686
22 May 20260.47451
26 May 20260.4686
12 Jun 20260.43957
14 Jun 20260.44834
15 Jun 20260.08682
16 Jun 20260.08557
27 Jun 20260.08404
22 Aug 20260.08521
28 Aug 20260.09157
2 Sep 20260.09238

69 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.09238Published2025-03-26CISA KEV2025-03-27Public PoC2025-04-06Index as of2026-09-04

Listed by CISA one day after it published, exploit probability more than doubled between 2025-03-27 and 2025-03-28 (0.01618 → 0.09213) and the record had been public for 1 year, 5 months when this index was last written.

Published 2025-03-26 receipt · CISA KEV 2025-03-27 receipt · Public PoC 2025-04-06 receipt · Index as of 2026-09-04 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-2783.

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.