LiveActive security incident?Get immediate response
CVE Record

CVE-2025-2783: Incorrect handle provided in unspecified circumstances in Mojo in Google Chrome on Windows prior to 134.0.6...

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)

HighCVSS 8.3Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2025-2783 is a high-severity Google Chrome for Windows flaw that could let an attacker escape Chrome's sandbox when a user opens a malicious file. CISA lists it as known exploited, so this is not a theoretical browser risk.

Executive priority

Treat this as an urgent browser patching item because it affects a widely deployed endpoint application and is listed by CISA as known exploited. The practical business goal is rapid version compliance across Windows devices.

Technical view

The issue is an incorrect handle condition in Chrome's Mojo component on Windows before 134.0.6998.177. The CVSS 3.1 score is 8.3 with network attack vector, high complexity, no privileges required, user interaction required, changed scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Organizations with Windows endpoints running Google Chrome versions earlier than 134.0.6998.177 are the relevant exposure. Risk is highest where users can receive and open untrusted files and where browser version enforcement is weak.

Exploitation context

CISA KEV listing supports known exploitation. The source bundle does not provide exploit details, indicators of compromise, affected non-Windows platforms, or evidence of broader product impact. User interaction is required according to the CVSS vector and CVE description.

Researcher notes

Available public details are limited. The Chromium issue is referenced, but the bundle does not include root-cause specifics beyond Mojo receiving an incorrect handle under unspecified circumstances. Avoid assuming exploit chains, payload formats, or affected platforms beyond Chrome on Windows.

Mitigation direction

  • Update Chrome on Windows to 134.0.6998.177 or later.
  • Use enterprise browser management to enforce the minimum version.
  • Prioritize remediation on systems handling email, downloads, and external files.
  • Review Google and CISA guidance for any newer remediation instructions.
  • Do not rely on the Chrome sandbox as the sole control.

Validation and detection

  • Inventory Chrome versions across Windows endpoints.
  • Confirm no managed Windows endpoint is below 134.0.6998.177.
  • Verify update policies cannot be deferred indefinitely.
  • Check CISA KEV tracking for organizational remediation status.
  • Review security telemetry for suspicious file-open and browser activity.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-2783 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.3 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H1.66Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.3High
CVSS 3.1 vector shape for CVE-2025-2783Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleChrome134.0.6998.177Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.