ChromeWeb browser · Google
CVE-2025-2783
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIncorrect 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)
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA sandbox escape vulnerability in Google Chrome's Mojo component on Windows (versions prior to 134.0.6998.177) allows remote attackers to escape the sandbox and potentially execute arbitrary code via a malicious file due to incorrect handle handling in unspecified circumstances.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 134.0.6998.177CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Chrome version via address barOpen Google Chrome on Windows, type chrome://version in the address bar, and press Enter. Locate the "Version" field displayed on the page.Affected if The displayed version number is lower than 134.0.6998.177 (for example, 134.0.6998.176 or earlier)
-
Check Chrome version via Help menuClick the three-dot menu icon in Chrome, select "Help", then select "About Google Chrome". The version number is shown in the resulting dialog.Affected if The displayed version number is lower than 134.0.6998.177
-
Confirm Windows platformVerify that the Chrome browser being checked is running on a Windows operating system, as this vulnerability only affects Chrome on Windows.Affected if Chrome is running on Windows and the version is below 134.0.6998.177
If Google Chrome on Windows is installed with a version lower than 134.0.6998.177, the environment is affected by this sandbox escape vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped134.0.6998.177
Update Google Chrome to version 134.0.6998.177 or later on all Windows systems. This is a user-initiated browser update but may require enterprise deployment tools in managed environments.
Chrome 134.0.6998.177 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Alternatively, enter chrome://settings/help in the address bar
- Chrome will automatically check for and download available updates
- Wait for the update to download (version 134.0.6998.177 or later)
- Click 'Relaunch' or 'Restart' to complete the installation
- Verify the update by returning to Settings > Help > About Google Chrome and confirming the version is 134.0.6998.177 or higher
- For enterprise deployments, use Chrome Enterprise bundle or Group Policy to deploy the update across managed devices
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2783 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data