ChromeWeb browser · Google
CVE-2025-10201
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 · uneditedInappropriate implementation in Mojo in Google Chrome on Android, Linux, ChromeOS prior to 140.0.7339.127 allowed a remote attacker to bypass site isolation via a crafted HTML page. (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 vulnerability in the Mojo messaging framework of Google Chrome on Android, Linux, and ChromeOS allows a remote attacker to bypass site isolation protections via a crafted HTML page. This could enable a malicious website to access sensitive data from another origin (cookies, tokens, local storage) that should be protected by the same-origin policy.
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
< 140.0.7339.127CVSS 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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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.
-
Confirm Google Chrome is installedOn Linux, run 'which google-chrome' or 'which chrome' in terminal. On Android, check if Chrome app is present in app settings. On ChromeOS, open the browser.Affected if Google Chrome browser is present on the system
-
Determine installed Chrome version on LinuxRun 'google-chrome --version' or '/opt/google/chrome/chrome --version' in terminalAffected if Command returns a version number less than 140.0.7339.127
-
Determine installed Chrome version on AndroidOpen Android Settings > Apps > Chrome > App info to view the version numberAffected if Version shown is less than 140.0.7339.127
-
Determine installed Chrome version on ChromeOSOpen chrome://version in the address bar and note the version listedAffected if Version listed is less than 140.0.7339.127
If the installed Google Chrome version is below 140.0.7339.127 on Android, Linux, or ChromeOS, the environment is vulnerable to site isolation bypass.
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 · scoped140.0.7339.127
Update Google Chrome to version 140.0.7339.127 or later on affected platforms (Android, Linux, ChromeOS). Site isolation is a critical security boundary; ensure browser updates are deployed promptly.
Chrome 140.0.7339.127 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Verify the current version number displayed
- If the version is below 140.0.7339.127, Chrome will automatically check for and install updates
- After the update completes, restart Chrome to apply the changes
- Alternatively, manually download the latest Chrome version from the official Google Chrome download page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10201 — 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-10201 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