CVE Tools

CVE-2025-2783

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. (Chrom...

Exploited in the wild. In CISA KEV since 2025‑03‑27. Fixed in 134.0.6998.177.

Check it yourself

OpenVAS · 7 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.836066

Run the check

Published Updated Sources: CVE.org, NVD, BDU, CSAF

What to do

Find your product and version, then upgrade to the build on the right.

  • Google ChromeAffected: ≥ 134.0.6998.177, < 134.0.6998.177Upgrade to: 134.0.6998.177Stated by: CVE record
  • Microsoft Corp Microsoft EdgeAffected: до 134.0.3124.93Upgrade to: not statedStated by: BDU
  • Palo Alto Networks Inc. Prisma Access BrowserAffected: до 134.29.5.178Upgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Coverage timeline

0 publishers
  1. Added to CISA KEV catalog

    ·CISA KEV

Sourced from public security reporting — each date is when it was published, not when it happened. 1 further article named this CVE in wider roundups without reporting it as a distinct event.

What it is

From the CVE record

COMOS is affected by multiple vulnerabilities that could allow an attacker to execute arbitrary code or cause denial of service condition, data infiltration or perform access control violations. Siemens has released new versions for the affected products and recommends to update to the latest versions.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS95th
CISA KEV
CISA KEV

Listed as exploited in the wild since 2025-03-27.

US federal agencies must remediate by 2025-04-17.

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

9.2% chance of exploitation activity in the next 30 days, which ranks it in the 95th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 456 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. EPSS band changemoderate → low
  3. Patch availablerecord updated
  4. Added to CISA KEV
  5. Publishedweakness classified

Affected products

And 2 more affected products. See all after sign-in

Technical detail

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

Scored 8.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction RequiredA user must click a link, open a file, or perform some action

Scope

  • Scope ChangedThe exploit can affect other components (e.g. sandbox escape, host compromise from VM)

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next exploited one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Chrome, not every advisory. This one: actively exploited.