dbcve.org
ChromeWeb browser · Google

CVE-2025-11458

HIGH · 8.1 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 141.0.7390.65 or later.
See remediation →
88/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Heap buffer overflow in Sync in Google Chrome prior to 141.0.7390.65 allowed a remote attacker to perform an out of bounds memory read 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 confidence

A heap buffer overflow vulnerability exists in Google Chrome's Sync component versions prior to 141.0.7390.65. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, causing the browser to read memory outside allocated heap buffers. This can lead to sensitive information disclosure via out-of-bounds memory reads.

MitigationUpdate Google Chrome to version 141.0.7390.65 or later. Organizations should deploy browser updates through their enterprise management tooling and verify fleet compliance.

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
Affected:< 141.0.7390.65

CVSS 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
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Google Chrome is installed
    Check for Chrome installation: On Windows, look in C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exe. On macOS, check /Applications/Google Chrome.app. On Linux, check /usr/bin/google-chrome or /opt/google/chrome/google-chrome.
    Affected if Chrome is not installed on the system
  2. Determine the installed Chrome version
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' from command line on Linux. On Windows, right-click chrome.exe, select Properties, and check the Details tab for File version.
    Affected if Unable to determine the installed version
  3. Compare installed version to the affected range
    Compare the version number found in the previous step to 141.0.7390.65. The vulnerability affects all versions prior to 141.0.7390.65 (e.g., 141.0.7390.64, 140.x.x.x, etc.).
    Affected if Installed version is less than 141.0.7390.65
  4. Verify if Sync feature is enabled
    Navigate to chrome://settings/syncSetup in Chrome. Check if sync is turned on or if the user has previously signed in and enabled synchronization features.
    Affected if Sync is enabled and the user is signed in; however, the vulnerability could still trigger even with sync configured but not actively syncing at attack time

A user is affected if they have Google Chrome installed with a version prior to 141.0.7390.65, regardless of Sync status, since a crafted HTML page could trigger the heap buffer overflow in the Sync component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 141.0.7390.65 or later
Fixed in 141.0.7390.65
Interim mitigation

Update Google Chrome to version 141.0.7390.65 or later. Organizations should deploy browser updates through their enterprise management tooling and verify fleet compliance.

Recommended fix High confidence

141.0.7390.65

  1. Open Google Chrome browser
  2. Navigate to Settings (click the three-dot menu in the top-right, then select 'Settings')
  3. Scroll to the bottom and click 'About Chrome' in the left sidebar
  4. Chrome will automatically check for updates; if version 141.0.7390.65 or later is available, click 'Update Google Chrome'
  5. Restart the browser to complete the update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-11458 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-11458 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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